bug-cvs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: cvs checkout -r and -D option is not exclusive


From: Kevin Wang
Subject: Re: cvs checkout -r and -D option is not exclusive
Date: Tue, 19 Feb 2002 16:21:22 -0800

I haven't tested if -r and -D and -f work correctly in 'checkout' but in 'update' they're definitely not working right.

My situation: CruiseControl, when doing its first build, deletes the compilation area and source tree and does a 'cvs checkout' with my -r and -f flags so that I can build a sparsely-branched branch.  When doing second and further builds, it first does a 'cvs log' (to see if there's anything changed that actually needs building) and then uses the same datestamp to do a 'cvs up' so that the files on disk match the log it already generated.

This is what breaks: "cvs up -f -r BRANCH -D DATESTAMP module_name"

The -f flag is ignored, and my respository is wiped 90% clean because "file doesn't exist" in the branch, that is.


In this message: http://mail.gnu.org/pipermail/bug-cvs/2000-March/001083.html
A fix is suggested.  I never saw a followup message, and there was a related message in the middle of 2001 here:

http://ccvs.cvshome.org/servlets/ReadMsg?msgId=13107&listName=bug

Help?

   - Kevin Wang

kwang@qabuild:~ $ uname -a
SunOS qabuild 5.8 Generic_108528-11 sun4u sparc SUNW,Ultra-4

kwang@qabuild:~ $ cvs --version

Concurrent Versions System (CVS) 1.11.1p1 (client/server)

Copyright (c) 1989-2001 Brian Berliner, david d `zoo' zuhn,
                        Jeff Polk, and other authors

CVS may be copied only under the terms of the GNU General Public License,
a copy of which can be found with the CVS distribution kit.

Specify the --help option for further information about CVS


reply via email to

[Prev in Thread] Current Thread [Next in Thread]