[p4] Question with use of labelsync

[Robert Cowham]

Just curious - which server version are you using?

C:\bruno_ws>p4 files @l3
@l3 - no such file(s).

C:\bruno_ws>
C:\bruno_ws>
C:\bruno_ws>p4 labelsync -l l3 //... at sybjam
//depot/main/jam/Build.com#5 - added
//depot/main/jam/command.c#6 - added
//depot/main/jam/command.h#4 - added
//depot/main/jam/compile.c#18 - added
//depot/main/jam/compile.h#4 - added
//depot/main/jam/execcmd.h#2 - added
//depot/main/jam/execnt.c#5 - added
//depot/main/jam/execunix.c#12 - added
//depot/main/jam/execvms.c#5 - added
//depot/main/jam/expand.c#5 - added

C:\bruno_ws>p4 files ...#have
...#have - file(s) not on client.

C:\bruno_ws>

i.e. the described behaviour works for me.

Note

C:\bruno_ws>p4 info
Server version: P4D/NTX86/2006.1/104454 (2006/08/02) 

Robert

> -----Original Message-----
> From: perforce-user-bounces at perforce.com 
> [mailto:perforce-user-bounces at perforce.com] On Behalf Of Steven W. Orr
> Sent: 17 August 2006 15:41
> To: Weintraub, David
> Cc: Perforce Users
> Subject: Re: [p4] Question with use of labelsync
> 
> On Wednesday, Aug 16th 2006 at 17:40 -0400, quoth Weintraub, David:
> 
> =>> Is there an easy way to copy a label without having to 
> populate a =>multigig workspace?
> =>
> =>Yes, use "p4 tag" instead of "p4 labelsync". The difference 
> between =>"tag" and "labelsync" is similar to the difference 
> in CVS between "tag"
> =>and "rtag".
> =>
> =>    $ p4 tag -l B //... at A 
> 
> Thanks. This explanation is useful but maybe highlights that 
> better docs are needed in the p4 help commands for tag and 
> labelsync, as well as in the PP O'Reilly book. The concise 
> syntax for p4 help labelsync is now officially confusing:
> 
>  > p4 help labelsync
> 
>     labelsync -- Synchronize label with the current client contents
> 
>     p4 labelsync [ -a -d -n ] -l label [ file[revRange] ... ]
> 
>         Labelsync causes the named label to reflect the 
> current contents
>         of the client.  It records the last revision of each 
> file taken
>         onto the client.  The label's name can subsequently be used in
>         a revision specification as @label to refer to the revision of
>         a file as stored in the label.
> 
>         Without a file argument, labelsync causes the label 
> to reflect the
>         contents of the whole client, by adding, deleting, 
> and updating the
>         label.  If a file is given, labelsync updates only 
> that named file.
> 
>         If the file argument includes a revision 
> specification, then that
>         revision is used instead of the revision taken by the 
> client.  If
>         the revision specified is a deleted revision, then 
> the label will
>         include that deleted revision.  See 'p4 help 
> revisions' for help
>         specifying revisions.
> 
>         If the file argument includes a revision range 
> specification, then
>         only files selected by the revision range are updated, and the
>         highest revision in the range is used.
> 
> The idea here is that
> p4 labelsync -l B ... at A 
> 
> will only work on a *populated* workspace is something that 
> needs to be clarified for future generations.
> _______________________________________________
> perforce-user mailing list  -  perforce-user at perforce.com 
> http://maillist.perforce.com/mailman/listinfo/perforce-user
> 
>