[Top][All Lists]

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

Re: cvs add <directory>

From: Mark D. Baushke
Subject: Re: cvs add <directory>
Date: Thu, 22 May 2003 13:57:41 -0700

Ross Patterson <address@hidden> writes:

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

If you want folks to be able to add top-level modules using 'cvs add', then
you probably want to add 


to your CVSROOT/config file.

After you have done that, then the following steps will add new-module
to your repository:

      cvs checkout -l .
      mkdir new-module
      cvs add new-module

In CVS versions prior to the existence of the TopLevelAdmin keyword, the
only way to create a new top-level module was to go to an empty directory
and cvs import a new module.

        -- Mark

reply via email to

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