Re: Unexpected directory-entry in CVS/Entries

2005-02-23 Thread Larry Jones
[EMAIL PROTECTED] writes: > > And exactly this is the core problem. I don't see a difference between > checking out two different projects on into the other or checking them > out into two different directories and moving them on into another. I > also can move any project root to some other lo

Re: Unexpected directory-entry in CVS/Entries

2005-02-23 Thread Larry Jones
[EMAIL PROTECTED] writes: > > 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). No, it's not crystal clear, bec

Re: Unexpected directory-entry in CVS/Entries

2005-02-23 Thread gnu-cvs
*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 PRO

Re: Unexpected directory-entry in CVS/Entries

2005-02-23 Thread gnu-cvs
Whether it should or not is open to debate, but it does not. And exactly this is the core problem. I don't see a difference between checking out two different projects on into the other or checking them out into two different directories and moving them on into another. I also can move any proje

Re: Unexpected directory-entry in CVS/Entries

2005-02-23 Thread Larry Jones
[EMAIL PROTECTED] writes: > > sub1/ > + sub2/ > > Situation a) > You have checked out sub1 and sub2 from the same repository (but > different locations in it). Invoking 'cvs update' in sub1 dives into > sub2. Invoking 'cvs update sub2/file2.txt' fetches the file. This is the correct behavior r

Re: Unexpected directory-entry in CVS/Entries

2005-02-23 Thread Larry Jones
[EMAIL PROTECTED] writes: > > 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? Whether it should or not is open to debate,

Re: Unexpected directory-entry in CVS/Entries

2005-02-23 Thread Larry Jones
[EMAIL PROTECTED] writes: > > As you can see, for some mysterious reason, CVS 1.12.11 creates an entry for > sub2 in the parent's CVS/Entries(.Log). 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 subdire

Re: Unexpected directory-entry in CVS/Entries

2005-02-23 Thread gnu-cvs
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: [repo

Re: Unexpected directory-entry in CVS/Entries

2005-02-23 Thread gnu-cvs
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 in

Unexpected directory-entry in CVS/Entries

2005-02-23 Thread gnu-cvs
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$ cvs-1.12.11