Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to sales@march-hare.com.
Lionello Lunesu wrote:
> Tony,
>
> I'm sorry I keep bothering you with this, but I have the feeling something
> strange is going on that can be fixed. Just some test results:
>
> It seems the empty module was checked out before the full one:
>
>
>>cvs -d:pserver:anonymous at cvs.sourceforge.net:/cvsroot/projx co -P XXXX
>>xxxx
>
>
> ("cvs co -P ." would proof the same thing but I don't care about the other
> modules in that repo)
> The module "XXXX" is empty, "xxxx" if full.
> The checkout succeeds, but the CVS\Repository file says "XXXX" (which it
> isn't)
> So the module name that the server sent to the client during the check-out
> was not the same as the module mentioned in CVS\Repository on the client?
The server sent two CVS/Repository files, both of which appear to the
client to be identical. When the second one arrives it is discarded as
there's no point in using it (the second checkout is treated as an
update, basically).
> From a "cvs co -P ." I've noticed that empty modules are not removed until
> cvs is finished with the check-out. If this behaviour could be changed
> (testing modules immediately after their check-out), the problem would be
> "solved".
CVS has always done this... it would be hard to justify changing it just
for this case.
Tony