Hi,
I have ran the test with the repo local to the CVS server, and it shows the
same behavior. Which brings me to the conclusion that the client/server
protocol does not function as expected. Here's the scenario: (Can be done by
the same user on the same machine)
1. Create the repository:
cvs -d
This happened with 1.10.8 and also with 1.11.1p1. No related fix has been
mentioned in the news file for CVS versions 1.12-1.15.
Shlomo
-Original Message-
From: Guus Leeuw jr. [mailto:[EMAIL PROTECTED]
Sent: Sunday, February 23, 2003 12:07 PM
To: Reinstein, Shlomo
Cc: [EMAIL PROTECTED]
We have a CVS-repository with a modules basicly like this:
# this will enable you to check out 'src'
src -d src/org/mmbase mmbase
# to check out everything
all -d mmbase all src config html documentation
It is possible to check out 'src' or 'all', or one of the other
top-level directories
Michiel Meeuwissen writes:
Having checked out 'src' though, and doing a 'cvs update -d -P' in the
src directory, all top-level directories are also added to src/org
directory:
That's the way it's always worked. CVS has no way to know whether a
missing directory is missing because it is new
Just do cvs up twice. The first time you'll get all the updates and
messages whizzing by, the second time, only the conflicts and your changes
will show up.
HTH
-Original Message-
Date: 21 Feb 2003 07:55:55 -0500
From: Steven Tryon [EMAIL PROTECTED]
To: richard blair [EMAIL PROTECTED]
