/contrib/cvs/MINOR-BUGS

 1Low-priority bugs go here.  Actually, most every documented bug is
 2"low-priority"--in the sense that if it is documented it means noone
 3has gotten around to fixing it.
 4
 5
 6* "cvs update -ko -p -r REV file" doesn't seem to pay attention to the
 7  '-ko', at least in client/server mode.  A simple work around is to
 8  temporarily change the db file with "cvs admin -ko file", then switch
 9  it back to the original modes after the checkout (probably '-kkv').
10
11* "cvs status" has a difference in its output between local and
12  client/server mode.  Namely there's a tab character followed by a
13  ctime(3)-style date string at the end of the "Working revision:"
14  field.
15
16* commands which don't work in a local working directory should probably
17  ignore any CVS/Root values and revert to using CVSROOT alone.  The
18  current use of CVS/Root can be very confusing if you forget you're in
19  a working directory for a remote module -- something that's very easy
20  to do since CVS hides the client operation very well, esp. for
21  commands which fail for this reason.  The only clue might be the word
22  "server" in a message such as this:
23	cvs server: cannot find module `patch' - ignored
24
25* cvs init may gave a strange error at times:
26	ttyp4:<woods@clapton> $ cvs -d /local/src-CVS init
27	cvs [init aborted]: cannot open CVS/Root: No such file or directory
28  but it seemed to work just the same....  Note that at the time CVSROOT
29  was set to point to a CVS server using the ":server:" option.
30
31* If a ~/CVS/Root file exists on the server and you are using rsh to
32connect to the server, CVS may loose its mind (this was reported in
33May 1995 and I suspect the symptoms have changed, but I have no
34particular reason to think the bug is fixed -kingdon, Sep 96).
35
36* (Jeff Johnson <jbj@jbj.org>)
37  I tried a "cvs status -v" and received the following:
38
39  ? CVS
40  ? programs/CVS
41  ? tests/CVS
42  cvs server: Examining .
43  ===================================================================
44  File: Install.dec            Status: Up-to-date
45  ...
46  
47  I claim that CVS dirs should be ignored.
48  (This reportedly happens if "cvs add CVS" (or "cvs add *")
49  is followed by "cvs status", in client/server mode - CVS 1.9).
50
51* On remote checkout, files don't have the right time/date stamps in
52  the CVS/Entries files.  Doesn't look like the C/S protocol has any
53  way to send this information along (according to cvsclient.texi).
54  Perhaps we can spiff it up a bit by using the conflict field for the
55  stamp on the checkout/update command.  Please note that this really
56  doesn't do very much for us even if we get it done.
57
58* Does the function that lists the available modules in the repository
59  belong under the "checkout" function?  Perhaps it is more logically
60  grouped with the "history" function or we should create a new "info"
61  function?