bug-cvs
[Top][All Lists]
Advanced

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

cvs ls corner cases


From: Alexander Taler
Subject: cvs ls corner cases
Date: Tue, 20 Sep 2005 21:16:42 -0400

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Tue, 20 Sep 2005 21:16:35 EDT

Hi All, I've just tried a couple of corner cases with cvs ls, and
I'm not sure that it's behaving the way it should.

1] If cvs ls is called with the name of a file which doesn't
   exist in the repository, no output is generated.  (It doesn't
   matter whether or not the file exists in the local directory.)

   This is somewhat counter to the behaviour of the shell command
   'ls', which prints a warning, and 'cvs st', which prints
   "Status: unknown".  Perhaps a warning on stderr would be
   appropriate in this case.  If this route is taken, should it
   also apply to files which exist, but not on the sticky
   tag/branch?

2] If a directory is specified in the local Entries file, but not
   in the repository, it will not appear in the output of 'cvs
   ls' if explicitly named on the command line, but it will
   appear if no files are specified:

$ echo D/miscreant//// >> CVS/Entries 
$ cvs-1.12 ls miscreant
$ cvs-1.12 ls          
eue
miscreant

   This behaviour should be consistent, at the very least.  I
   guess that this works this way because of how modules work in
   CVS.  It's ok to have a subdirectory in the sandbox which
   doesn't match a subdirectory in the repository because it
   might be mapped elsewhere in the repository.  Perhaps it
   should check if the directory actually exists locally, and has
   a 'CVS' subdirectory.

I would have written sanity.sh test cases for these, but I wasn't
at all sure how they should work.  :)

Alex   

- -- 
https://savannah.gnu.org/projects/libcvs-spec    Access CVS through a library.
PGP:  ID: 0x23DC453B  FPR: 42D0 66C2 9FF8 553A 373A  B819 4C34 93BA 23DC 453B
The pimp's trade must be carried out by intelligent people, is essential to any
well-ordered society, and should have an official inspector.  -- Don Quixote
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (OpenBSD)
Comment: Processed by Mailcrypt 3.5.8 <http://mailcrypt.sourceforge.net/>

iD8DBQFDMLR6TDSTuiPcRTsRAhXrAJ9iAVPG+6koTh8/eDPYG7J/GnNPvQCfUeX1
iyVAKmUvSlJUlPgdbJV1VQ8=
=LG/Q
-----END PGP SIGNATURE-----




reply via email to

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