Re: Adding a Tag After the Fact

[Jake Colman]

>>>>> "DJ" == Dennis Jones <address@hidden> writes:

   DJ> "Jake Colman" <address@hidden> wrote in message 
   DJ> news:address@hidden
   >> 
   >> We forgot to tag our release branch after the last two minor releases.
   >> I now need to rebuild the release prior to this.  So, for example, our
   >> branch was tagged with XXX_5_1_RELEASE but was not tagged with
   >> XXX_5_1_1_RELEASE and XXX_5_1_2_RELEASE.  If I know the dates that
   >> 5.1.1 and 5.1.2 were released, how can I add those missing tags to the
   >> branch.
   >> 
   >> TIA!

   DJ> I won't be so rude as to suggest that you RTFM, but it couldn't
   DJ> hurt...

   DJ> If you had just asked CVS how to do it (cvs -H tag), it would have
   DJ> told you the following (and you wouldn't even have to RTFM!):

   DJ> cvs tag [-D date] tag [files...]

   DJ> and/or for a branch tag:

   DJ> cvs tag -b [-D date] tag [files...]

Dennis,

I appreciate the 'RTFM' and the 'cvs -H' suggestion but if you look closely
you will see that neither solve my problem.

I need to tag a specific branch with a new symbolic tag for al revisions as
of a specified date.

Are you suggesting I do the following:

  cvs co -r <branchname>        # checks out branch tip
  cvs tag -D <date> NEW_TAG     # only tags revisions as of date?

Because it is not clear to me that that will work.

Others have suggested using rtag but then how do I tell rtag which branch
should be tagged?

...Jake

-- 
Jake Colman
Director of Software Development
Principia Partners LLC
101 West Elm Street
Suite 620
Conshohocken, PA  19428
+1 (610) 755-9786
www.principiapartners.com