/contrib/cvs/MINOR-BUGS

https://bitbucket.org/freebsd/freebsd-head/ · #! · 61 lines · 50 code · 11 blank · 0 comment · 0 complexity · 26f538e50cd65a37706f30463dc49f88 MD5 · raw file

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