***************************************************************
Chris Cameron Open Telecommunications Ltd
Product Manager IN Product Management
[EMAIL PROTECTED] P.O.Box 10-388
+64 4 495 8403 (DDI) The Terrace
fax: +64 4 495 8419 Wellington
cell: +64 21 650 680 New Zealand
Life, don't talk to me about life ....(Marvin - HHGTTG)
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of
> Eric Siegerman
> Sent: Thursday, 12 July 2001 7:22 a.m.
> To: [EMAIL PROTECTED]
> Subject: Re: Sticky tags
>
>
> --- irina sturm <[EMAIL PROTECTED]> wrote:
> > I don't understand: if I am doing what you say,
> > I am not preserving myself of integrating the
> > other users' modifications before finishing
> > with my own, but just doing the same as for file_1.
>
> To do this (i.e. make and commit changes without (yet)
> integrating other peoples' changes), you'd need to create a
> branch.
>
> > In which case also I can't understand what the
> > sticky [non-branch] tag is useful for.
>
> Not that much, really, IMO. I suspect that they weren't really
> designed into CVS, but came about as a side-effect of
> sticky-branch-tag support -- the code just lets you make *any*
> tag sticky.
>
We use non branch sticky tags for preserving 'contours' through our code
(e.g. release 1.0, integration build 2, etc.). This is very usefull for
determining changes from one 'release' to another and also for ensuring that
we can always deliver the same 'release'.
_______________________________________________
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs
