Issue #418
aliased entries in s4_state cause warnings on s4 update
| Status: | New | Start date: | 11/07/2011 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | Wilson Snyder | % Done: | 0% |
|
| Category: | - | |||
| Target version: | - |
Description
Given this initial Project.viewspec:
set EMPTY ^/void view ^/dvtools/trunk area1After the initial
s4 checkout or s4 update, the s4_state file has aliased entries. Only 'area1' is required.
# S4 State File
$VAR1 = {
'viewspec_hash' => '60a28c644967d5f7ecf706126f7845fb',
'viewspec_managed_switches' => [
'area1',
'/export/dv12/bdobbie/s4-test/area1'
]
};
1; # so that require of this file will work
If the Project.viewspec is changed to:
set EMPTY ^/void view ^/dvtools/trunk area1 view ^/dvtools/trunk area2
s4 update gives a spurious info message:
$ s4 update <snip> Updated to revision 94203. s4: Remove unused switchpoint /export/dv12/bdobbie/s4-test/area1The s4_state file now shows the correct entry for 'area1', but now 'area2' has an aliased entry.
# S4 State File
$VAR1 = {
'viewspec_hash' => '67d045e94eeeac56c4619f2fdefbf29d',
'viewspec_managed_switches' => [
'area1',
'area2',
'/export/dv12/bdobbie/s4-test/area2'
]
};
1; # so that require of this file will work
This issue is minor, but it can be very confusing to a user when he or she sees a bunch of these messages unexpectedly.
History
Updated by Brad Dobbie over 1 year ago
An even more simple case that exhibits the issue is as follows.
Initial Project.viewspec:view ^/void area1Update the working copy to get area1:
$ s4 up At revision 94208. s4: Updating area1 At revision 94208.Change Project.viewspec to:
view ^/void area1 view ^/void area2Update the working copy to get area2:
> s4 up At revision 94208. s4: Updating area1 At revision 94208. s4: Updating area2 At revision 94208. s4: Remove unused switchpoint /export/dv12/bdobbie/s4-test/area1
The supurious message can be seen about /export/dv12/bdobbie/s4-test/area1.
Also available in: Atom
![[logo]](/img/veripool_small.png)