[p4] Tracking Label Contents

[Robert Cowham]

If you use the new dynamic labels and have a spec depot then you get the
best of both worlds - versioning and easy labelling.

Of course this means that the label must point to a specific changelist, but
that's good practice anyway I would have thought.

The one drawback is that the "p4 labels" command doesn't work for dynamic
labels. I can understand why in principle, but it would be really nice if
Perforce updated this command to address the one case of pointing to a
changelist - hardly a big extra lookup. This one optimisation would address
at least 80% of the requirement.

Robert

> -----Original Message-----
> From: perforce-user-bounces at perforce.com 
> [mailto:perforce-user-bounces at perforce.com] On Behalf Of paul goffin
> Sent: 14 June 2007 07:39
> To: Jamison, Shawn
> Cc: perforce-user at perforce.com
> Subject: Re: [p4] Tracking Label Contents
> 
> If you don't implement a 'tip revision is always clean' 
> policy (and I strongly believe you shouldn't - certainly not 
> in the development branch), you need a way to identify the 
> 'last clean revision'.
> 
> And a potential good way to do that is a label.
> 
> Trouble is when that label is moved to a non-clean build, 
> there's no way to find out what it used to point to.
> 
> Obviously this can be avoided by a _policy_ of always 
> creating new labels but policies get broken by well meaning 
> individuals.
> 
> Paul
> 
> Quoting "Jamison, Shawn" <sjamison at ciena.com>:
> 
> > I guess I'm naive but why track the contents of a label?  
> > 
> > I just can't envision a usage model that would require this.
> > 
> > -Shawn J>
> > Perforce Admin
> _______________________________________________
> perforce-user mailing list  -  perforce-user at perforce.com 
> http://maillist.perforce.com/mailman/listinfo/perforce-user
>