Re: tag dates

[Torbjörn Axelsson]

"McCann, Brian" <address@hidden> writes:

> Larry,
> 
> So when I run a tag against our source code it just tags the code
> i.e. PCS-1-0-0-Build30 and there is no date associated in the history file
> for when that cvs command was run? The problem at hand is I know the date
> of the build I'm looking for May 17th, but to get that code I need the tag 
> done on that date.
> 


Ok, so it is a case of "damage recovery". I would say that you pick
any file that was likely changed both May 17th and May 18th.

Check out that file as it was some time between the previous
build and the build you are looking for, say lunch May 17th.
Remember what version it was.

Check it out again for lunch May 18th. (Assuming _nightly_ builds
here.)

Hopefully you get say 1.57 and 1.98 (busy coders there) and just one
"PCS-1-0-0-Build[0-9]+" tag in the interval between them. That should
be your tag.

An example:
$ cvs update -D "2001-05-17 12:00" -p often_changed_file >/dev/null 
===================================================================
Checking out often_changed_file
RCS:  /somewhere/often_changed_file,v
VERS: 1.57
***************


Just make sure you do not have 'cvs -q' in you ~/.cvsrc when you do
this.


Finding your tag can be done in the same way, pick a tag you believe
is fairly close to the correct date and check what version you get.

$ cvs update -r PCS-1-0-0-Build12 -p often_changed_file >/dev/null 
Checking out often_changed_file
RCS:  /somewhere/often_changed_file,v
VERS: 1.12
***************

$ cvs update -r PCS-1-0-0-Build30 -p often_changed_file >/dev/null 
Checking out often_changed_file
RCS:  /somewhere/often_changed_file,v
VERS: 1.257
***************

Use a binary search or just calculate where you should be. Happy
hunting.

Now, I know there has to be a smarter way to do this but this popped
out of my head right off.

/Torbjörn