[Top][All Lists]

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

Re: cvs add <directory>

From: Greg A. Woods
Subject: Re: cvs add <directory>
Date: Thu, 22 May 2003 18:31:49 -0400 (EDT)

[ On Thursday, May 22, 2003 at 16:08:27 (-0400), Ross Patterson wrote: ]
> Subject: Re: cvs add <directory>
> 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".

Yeah, the manual's wrong.  I've posted fixes to this part of the manual before.

> 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.

Yes, unfortunately though people seem to think for some bizarre reason
that directories contain something interesting other than just files and
thus they seem to want to version them, but fortunately they are
completely mistaken, or have been mislead by stupid unnecessary features
in other similar tools.  It all stems from the fact that far too many
people are using _very_ wrong tools for the jobs they think they're
trying to do.

                                                                Greg A. Woods

+1 416 218-0098;            <address@hidden>;           <address@hidden>
Planix, Inc. <address@hidden>; VE3TCP; Secrets of the Weird <address@hidden>

reply via email to

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