Re: Problem with recursive cvs edit command

[David Fuller]

There are a lot of weird behaviors with ampersand modules because they
aren't fully implemented.  This appears to be one of them.

On Wed, 6 Feb 2002, Dan wrote:

> OK,
> 
> I'm new to cvs, and think I've got everything working except for one
> peculiarity.
> 
> I've got a modules file that looks like:
> 
> moduleA -d moduleA path1/moduleA
> moduleB -d moduleB  path1/moduleB
> AllModules &moduleA &moduleB
> 
> I then checkout AllModules and end up with a directory tree locally like:
> 
> AllModules
>     moduleA
>     moduleB
> 
> which is what I would expect.  I can commit, get status, get logging, etc.
> at any point in the tree and everything works just fine.
> 
> If however I do a 'cvs edit' on moduleA, and moduleA has sub-directories
> (let's say suba for example - which has a file in it called filea), then I
> get the following error:
> 
> cvs -z9 edit (in directory C:\AllModules\moduleA)
> 
> cvs [edit aborted]: cannot find suba/filea: No such file or directory
> 
> *****CVS exited normally with code 1*****
> 
> If I do a 'cvs edit' on 'suba' directly however it works fine, and all the
> files in suba are marked edit:
> 
> cvs -z9 edit (in directory C:\AllModules\moduleA\suba\)
> 
> *****CVS exited normally with code 0*****
> 
> Any help for this novice cvs user would be greatly appreciated.
> 
> Dan
> 
> 
> 
> _______________________________________________
> Info-cvs mailing list
> address@hidden
> http://mail.gnu.org/mailman/listinfo/info-cvs
>