A "cvs ls" command is enough to provide browsing capabilities. I know scripts
can (and have been) written to perform this functionality, but a true "cvs ls"
would be much faster.
"cvs cd" and "cvs pwd" have the problems of having to keep state (ie "what is
the pwd").
The security need not be through obscurity. From what I see, by using pserver
and file permissioning, one need not rely on obscurity.
Noel
[EMAIL PROTECTED] on 05/05/2000 10:55:20 AM
To: [EMAIL PROTECTED]
cc: [EMAIL PROTECTED], [EMAIL PROTECTED] (bcc: Noel L Yap)
Subject: Re: "cvs checkout -c" again
On Fri, May 05, 2000 at 11:29:17AM -0600, Win32 M$ wrote:
> Agree, it should. Or, should we have 'cvs ls' and 'cvs cd' and 'cvs pwd' to
> "walk" the tree in the repository?
I like that solution. (We already have 'cvs rm', after all...)
> This question comes back again and again simply because it is so very
> natural and obvious to try to walk the tree in the repository that I think
> everybody is shocked when they discover for the first time that is't not
> available in CVS.
I sure was. For that matter, I still am.
On the one hand, I can see the security (albeit purely by obscurity) factor
in not allowing people to find out about projects other than by being
explicitly told about them (either by direct contact ("Hey, Joe - grab the
doc project!") or by putting them in CVSROOT/modules). On the other hand,
though, there's the nuisance factor of having to do the telling.
--
The Shortest Windows Manual: "Turn off the power switch."
Geek Code 3.1: GCS d- s+: a- C++ UL++$ P+>+++ L++>++++ E- W--(++) N+ o+ !K
w---$ O M- !V PS+ PE Y+ PGP t 5++ X+ R++ tv- b++ DI++++ D G e* h+ r++ y+
This communication is for informational purposes only. It is not intended as
an offer or solicitation for the purchase or sale of any financial instrument
or as an official confirmation of any transaction. All market prices, data
and other information are not warranted as to completeness or accuracy and
are subject to change without notice. Any comments or statements made herein
do not necessarily reflect those of J.P. Morgan & Co. Incorporated, its
subsidiaries and affiliates.
