[p4] How do YOU identify the code set for a release?

[Steve M. Robbins]

Hello,

On Fri, Jan 04, 2008 at 09:10:13AM -0500, todd.benham at kodak.com wrote:
> When I was testing labels (without scripts), I was able to do something
> like this:
> p4 tag -l V01.00.00 //depot/MAIN/source

True.  I should have prefaced my rant about labels in Perforce by
specifying that I'm only interested in "automatic" labels.

I believe your example creates a "static" label.  I never found a
1-liner to create an automatic label.  If I can be proved wrong, I can
get rid of my script!

Thanks,
-Steve
 
> -----Original Message-----
> From: perforce-user-bounces at perforce.com
> [mailto:perforce-user-bounces at perforce.com] On Behalf Of Shawn Hladky
> 
> >
> > So option #1 is to use a label.  Coming from years of CVS use, this is 
> > what I naturally gravitated to.  I was a little surprised that 
> > creating a label is so cumbersome; e.g. it involves filling out a 
> > form.  But I created a small script to turn it back into a one-liner 
> > similar to what one does in CVS.
> >
> > I know there are both 'static' and 'automatic' labels; let's assume we 
> > would only ever care to release at a changelist, so we use only 
> > automatic labels where the Revision: field is a changelist number.  My 
> > script essentially takes the label string and a changelist number, 
> > then creates and submits the appropriate form.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://maillist.perforce.com/pipermail/perforce-user/attachments/20080107/cac137d8/attachment.bin