here is some CVS info for those who will find it useful:
if the most recent changes checked in have inadvertently broken the
code, but you don't want to revert all the way back to the last tagged
version, here are some tools to help.
a) you can use the emacs 'C-x v a' command to update the ChangeLog, and
read a chronological log of all the checkins to find the problem.
b) use the cvs history command to find out exact times of the suspect
checkins
the options are: a=all users, c=list checkin's, D=date, f=files
cd BlastLib2; cvs history -acD 2003-04-06 -f *
M 2003-04-08 17:58 +0000 zhangchi 1.1.2.10 TBLPidRecon.cc ...
...
M 2003-04-08 18:41 +0000 zhangchi 1.10.2.62 TBLRecon.cc ...
M 2003-04-08 18:44 +0000 chris2 1.6.2.32 TBLDetRecon.cc ...
...
M 2003-04-08 18:44 +0000 chris2 1.1.2.13 recon.cc ...
c) then you can update to a specific point in time. note: for
BlastLib2, remember to user '-rv2' together with the time option, and
put +0 on the end of the time to avoid time zone issues.
spud1:~/blast/l 17:01> cvs up -rv2 -D'2003-04-08 18:44 +0'
TBLRecon.cc; cvs stat TBLRecon.cc|grep Working
Working revision: 1.10.2.62 Tue Apr 8 21:01:14 2003
- spud1:~/blast/l 17:01> cvs up -rv2 -D'2003-04-08 18:45 +0'
TBLRecon.cc; cvs stat TBLRecon.cc|grep Working
Working revision: 1.10.2.63 Tue Apr 8 21:01:35 2003
--chris
This archive was generated by hypermail 2.1.2 : Mon Feb 24 2014 - 14:07:29 EST