Aryeh M. Friedman wrote:
I maintain a local repo of the via the cvs mode of cvsup. When I do a:
What command did you use to check out the files, and what tree are you
talking about?
cvs -q -d /home/ncvs update
It will update any modified files but will not add any new files
When you
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Doug Barton wrote:
Aryeh M. Friedman wrote:
I maintain a local repo of the via the cvs mode of cvsup. When I
do a:
What command did you use to check out the files, and what tree are
you talking about?
cvsup -h cvsup9.us.freebsd.org
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Aryeh
M. Friedman
I maintain a local repo of the via the cvs mode of cvsup.
When I do a:
cvs -q -d /home/ncvs update
It will update any modified files but will not add any new
files (it
On Mon, 21 Jan 2008, Greg Larkin wrote:
cvs -q -d /home/ncvs update -d
The -d option given to the update subcommand builds directories the way cvs
checkout does. Without it, update will only operate on directories that are
already in your sandbox.
In principle you only need to specify
On Thu, Mar 18, 2004 at 01:49:07PM +0300, Dmitry Morozovsky wrote:
Dear colleagues,
maybe I'm stupid and blind ;-) but I still can't fugure out how can I ask CVS
to get diff between two states of a branch with known dates (such as today and
yesterday). All that I found was 'cvs get
On Thu, 18 Mar 2004, Ruslan Ermilov wrote:
RE maybe I'm stupid and blind ;-) but I still can't fugure out how can I ask CVS
RE to get diff between two states of a branch with known dates (such as today and
RE yesterday). All that I found was 'cvs get -jBRANCH:date1 -jBRACH:date2' but
RE this
In article [EMAIL PROTECTED],
Archie Cobbs [EMAIL PROTECTED] wrote:
Hmm.. sounds like we should do one or both of these things..
1/ Fix the bug in CVS that caused the import to set two different dates
I finally got around to checking, and the bug doesn't exist in the
current version of
[ CVS has screwy behavior ]
CVS has a heuristic that does the wrong thing for this particular
file.
[ Code and discussion deleted ]
I hope current
versions of CVS force the dates to be the same on an import. I
haven't checked to see whether that's the case or not.
Suggestions like this
Nate Williams writes:
I hope current
versions of CVS force the dates to be the same on an import. I
haven't checked to see whether that's the case or not.
Suggestions like this would be good to send to the new CVS maintainers.
Checkout www.cvshome.org, and send in a bug report, if you
In article [EMAIL PROTECTED],
Archie Cobbs [EMAIL PROTECTED] wrote:
Consider this source file:
http://www.freebsd.org/cgi/cvsweb.cgi/src/usr.sbin/xntpd/lib/Attic/ranny.c
Question: what version should this command checkout?
$ cvs co -D 'January 18, 1999 0:00'
John Polstra writes:
$ cvs co -D 'January 18, 1999 0:00' freebsd/src/usr.sbin/xntpd/lib/ranny.c
Perhaps version 1.1.1.2 would be correct, but instead you get 1.1.
CVS has a heuristic that does the wrong thing for this particular
file. The code is around line 3252 of
At 1:56 PM -0600 5/15/00, Warner Losh wrote:
I have a CVS question. Normally I wouldn't bother the nice folks here
with it, but since it involves backmigrating the local changes Timing
Solutions has made to FreeBSD, I thought that others might find its
answer useful in the future.
I would be
12 matches
Mail list logo
