Hi,
I have a simple project in the repository:
[repository-root]
+ test/
+ sub1/
| + test1.txt
+ sub2/
+ test2.txt
Now I check out test/sub1 and test/sub2 nested in each other:
[EMAIL PROTECTED]:~$ mkdir cvstest
[EMAIL PROTECTED]:~$ cd cvstest
[EMAIL PROTECTED]:~/cvstest$
Hi Larry,
Thanks for the response.
No mystery, just a bit of overloading. In addition to the list of
CVS-controlled files, the Entries file also contains a list of the known
subdirectories of the current directory (to avoid having to scan the
entire directory for subdirectories every time).
But
What, if I check out test/sub1 and test/sub2 in two different
directories and then move the sub2 into the sub1 directory? Shouldn't
this produce the same results as with the two different checkouts as
shown below?
Tom
[EMAIL PROTECTED] wrote:
Hi,
I have a simple project in the repository:
*WHAT* error message?!?
I thought, in this case it was crystal clear: something like
sub2/file2.txt is not available in the repository, because the
sub2-stuff comes from a different repository than the one from the
current working directory (sub1).
--
Cheers,
Tom
Larry Jones wrote:
[EMAIL
Using the diff command is no option, because it uses E responses instead of
sending the file content. This causes major troubles with non-ASCII-characters.
--
Best regards,
Thomas Singer
_
smartcvs.com
Jim.Hyslop schrieb:
Thomas Singer wrote:
We've encountered a problem with GNU CVS
Just to prevent an out-of-the-brain change: if they would we sent to stdout,
this would break at least SmartCVS.
--
Best regards,
Thomas Singer
_
smartcvs.com
Harald Dunkel schrieb:
Jim.Hyslop wrote:
I can't comment on why these messages go to stderr instead of stdout, but I
will
but I am sure that it can
read from cvs' stdout instead of stderr, too.
Yes, it *could*. But at the moment it expects this particular input from
stderr and all (?) other versions of CVS servers send it at stderr.
There are already too much differences between GNU CVS and CVSNT...
Wouldn't
