Hi Rob,
I'm not trying to pull an old snapshot of the code. The build script
checks out the tree based on the current timestamp using "`date`".
This timestamp is embedded in the target load, so that developers can
reproduce the code base, based on this timestamp.
I would expect that files which were previously removed from CVS, would NOT
get checked out in my workspace, if I were to use the current timestamp.
Regards,
Mal
Rob Helmer wrote:
On Tue, Nov 13, 2001 at 05:48:27PM -0800, Malcolm Fernandes wrote:
Hi,
We are using CVS 1.11.1p1 on Solaris. When we use 'cvs co -D date' on
the Main branch, I noticed that files which were previously 'cvs
removed' now get checked out in my workspace. This problem does not
happen on release branches 'cvs co -D date -rREL_X_Y'.
Is this a CVS bug? Any workarounds?
Hi Malcom,
Not sure I know what behaviour you expect, but as far as I
understand it, when you "cvs remove" a file a new revision is
added to the file with the status "dead".
If you pull up an older revision of the file, or cause an older
revision to be pulled up because it has a tag or date stamp associated
with it, then the older revision is brought into your working directory
because it's status is not "dead".
I think the basic question is, why do you not want to be able to pull
up an old "snapshot" of the code, as it was at the date/time specified,
when you do a "cvs co -D date", including removals and additions?
What behaviour do you expect?
HTH,
Rob Helmer
Namodn
_______________________________________________
Info-cvs mailing list
address@hidden
http://mail.gnu.org/mailman/listinfo/info-cvs
_______________________________________________
Info-cvs mailing list
address@hidden
http://mail.gnu.org/mailman/listinfo/info-cvs