[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

3 module related bugs

From: Dieter Maurer
Subject: 3 module related bugs
Date: Thu, 18 Sep 2003 09:52:37 +0200

Dear CVS community,

the attached "cvsroot.tar.bz2" demonstrates 3 module related bugs,
all revealed by "cvs -d <root> co MRoot".

1. Bad "CVS/Repository" for modules of the form MNAME -d X/Y/... DIR

   "cvs" puts "." (rather than "CVSROOT/EmptyDir") in "X/CVS/Repository".

   The effect: an updating "checkout" will put the complete
   CVS content in "X".

2. Apersand modules only get sometimes an entry in "CVS/Entries".
   In the example, "&MDir" and "&MRest" are inserted (as "x" and "MRest")
   in "MRoot"s "CVS/Entries" while "&MAmp" is not.

   Not placing an ampersand module in "CVS/Entries" has 2 adverse

    i)  an updating "checkout" marks the missing module as unknown,
        "? MRoot/MAmp" in the example.

    ii) an "update" does not recurse into the ampersand module.
        This may be a feature but is, at least, confusing.

3. An updating "co"
   does not respect restrictions in module definitions of the

        MNAME   DIR file1 file2 ...

   While the initial checkout only checks out the specified files,
   an updating checkout checks out the complete "DIR".

   The example demonstrates this in "MRoot/MRest".
   The initial checkout just places "f1" in this folder
   while an updating checkout adds "f2".

Version: Concurrent Versions System (CVS) (client/server)
Platform: Linux (SuSE 8.1)

I will work on bug 1 and 3 above.
Issue 2 may be a feature. I will wait for your opinions.


Attachment: cvsroot.tar.bz2
Description: Bzip2 compressed tar archive of a CVSROOT

reply via email to

[Prev in Thread] Current Thread [Next in Thread]