[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: Organising tags for an automated build system
From: |
Dale . Miller |
Subject: |
RE: Organising tags for an automated build system |
Date: |
Thu, 16 May 2002 17:10:15 -0500 |
Andy,
Use the -F option with tag or rtag to Move tag if it already exists.
cvs tag -F -r rev tag [files...]
like
cvs tag -F -r HEAD AUTOMATED-BUILD [files...]
Use tag for updating tags of files in your work area
or use rtag for updating tags of all [files...] in the repository.
Usage: cvs tag [-bcdFflR] [-r rev|-D date] tag [files...]
-b Make the tag a "branch" tag, allowing concurrent
development.
-c Check that working files are unmodified.
-d Delete the given tag.
-F Move tag if it already exists.
-f Force a head revision match if tag/date not found.
-l Local directory only, not recursive.
-R Process directories recursively.
-r rev Existing revision/tag.
-D Existing date.
> -----Original Message-----
> From: Glew, Andy [mailto:address@hidden
> Sent: Monday, May 13, 2002 12:32 PM
> To: address@hidden; address@hidden
> Subject: RE: Organising tags for an automated build system
>
>
> > If I use a date-based tag format like AUTOMATED-BUILD_{DATE}
> > I end up writing scripts that figure out which tag is the
> > most recent tag
> > for every module.
> > If I use a general tagname like AUTOMATED-BUILD I think I need
> > to remove such a tag before a new one is created ? Or does
> > cvs automagically
> > assumes that I need the most recent one ?
>
> I've always had to embed the date in the tag.
> In addition, I may have a floating tag without a date,
> but it has to be moved.
>
> I *wish* that CVS would allow multiple instances of the
> same tag for a file. I would use the latest, or,
> if I have a non-current version checked out, possibly
> the most recent tag.
>
> I.e.
>
> for a tag XXXX that occurs multiple times in the same file
> select
> * most recent version of that tag on the main branch
>
> * most recent version of that tag on a specified branch
> * most recent version of that tag on a specified branch
> (or its ancestors)
> that is older than a given version or time.
> * ... newer
>
> * most recent version of the tag on any branch
> ... newer/older
>
> I spend an awful lot of time trying to figure the above out
> from the log myself.
>
> I *wish* that CVS recorded the date/time at which a tag was
> applied.
>
> However, this doesn't obviate the need for creating a tag
> that has the date or something else tying it together...
> Most of us create our own script for that.
>
> _______________________________________________
> Info-cvs mailing list
> address@hidden
> http://mail.gnu.org/mailman/listinfo/info-cvs
>