Greetings,
One of our developers has reported the following behaviour from CVS. I
think I've found in the update code where this behaviour, the question is
whether there is a reason for this behaviour? Our developer expected the
timestamp to revert to the original co timestamp.
% cvs co foo/bar.cc
% cd foo
% ls -l
% rm bar.cc
% cvs update bar.cc
% ls -l
% rm bar.cc
% vi CVS/Entries (remove the line for bar.cc)
% cvs update bar.cc
% ls -l
The checkout gets the correct timestamnp on the file.
The first update gives bar.cc a timestamp which corresponds to the
time you issued the update command.
The second update give bar.cc the timestamp of the original
checkin time of bar.cc
***************************************************************
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)
_______________________________________________
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs
