Re: cvs add <directory>

[Ross Patterson]

On Wednesday 21 May 2003 04:29 pm, Greg A. Woods wrote:
> Use of "cvs add" is always best.  Only use "cvs import" if you're
> actually tracking third party sources and using the vendor branch
> support in CVS.

Section 3.1.3 of the CVS manual suggests that "cvs import" is also the correct 
way to add a new "project" in the top-level directory of the repository.  
That's always seemed odd to me, but it appears to be the *only* way to do 
that - "cvs add" refuses with "cvs [add aborted]: there is no version here; 
do 'cvs checkout' first".

> Note that directories in CVS (especially in the repository) are
> placeholders only.  They simply help to keep files in separate places so
> that they don't all clutter the top level.

One could say that about directories in general.  Perhaps we ought to return 
to the glorious days of flat file systems?  It seems to me that directories 
is CVS serve exactly the same purpose as directories in any file system - 
they help organize your files and prevent conflicts over naming.
-- 
Ross A. Patterson
Chief Technology Officer
CatchFIRE Systems, Inc.
5885 Trinity Parkway, Suite 220
Centreville, VA  20120
(703) 563-4164