Re: Unexpected directory-entry in CVS/Entries

[Larry Jones]

gnu-cvs@regnis.de 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 location on my disk and any 
> CVS command works. Why not in this situation?

Because somewhere along the way, one of the CVS developers thought that
it was a small price to pay to avoid having to scan the entire directory
for newly created, moved, or renamed subdirectories to recurse into
every time you issue a CVS command.  It also allows CVS to ignore any
subdirectories that your build process creates rather than trying to
recurse into them.  I don't think it's unreasonalbe to expect you to use
CVS commands to manipulate the contents of CVS-controlled directories
rather than expecting CVS to figure out what you intended when you
changed things around behind its back.

-Larry Jones

Pitiful.  Just pitiful. -- Calvin