[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 14:21:17 -0700

Hi Larry,

Thank you for the corrected information.


I agree with Larry, you probably want to use:

  cvs checkout -l -d toplevel .
  cd toplevel
  mkdir new-module
  cvs add new-module

to create new modules in the top-level.

        -- Mark

>Subject: Re: cvs add <directory>
>To: address@hidden (Mark D. Baushke)
>Date: Thu, 22 May 2003 17:15:48 -0400 (EDT)
>From: address@hidden (Larry Jones)
>Mark D. Baushke writes:
>> If you want folks to be able to add top-level modules using 'cvs add', then
>> you probably want to add 
>>     TopLevelAdmin=yes
>> to your CVSROOT/config file.
>No, you don't.  TopLevelAdmin causes a directory to be put under CVS
>control when you do a checkout *in* it, which you almost never want. 
>That is, if you do:
>       cvs co module
>your current directory gets a CVS subdirectory rather than just module
>and its subdirectories getting one.
>> 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
>That works reguardless of whether TopLevelAdmin is set or not, although
>I strongly suggest using -d to let checkout create a new directory
>rather than checking out into the current directory.
>> 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.
>Not so, the above has "always" worked.
>-Larry Jones
>My brain is trying to kill me. -- Calvin

reply via email to

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