[Top][All Lists]

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

Re: Erase all cvs info from directory tree

From: Mark E. Hamilton
Subject: Re: Erase all cvs info from directory tree
Date: Mon, 17 Oct 2005 13:21:41 -0600
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.3) Gecko/20040913


address@hidden wrote:
RobE <address@hidden> wrote:

Additionaly / alternatively: is there a way to import a project that
already has CVS information?

Well, you could do:

    shellprompt> find . -name CVS | while read d; do
        mv $d $d-orig
    shellprompt> cvs import blabla_the_usual ...

This renames the CVS directories to something harmless,
so they get imported like the rest.  They are treated like
ordinary directories and the information they contain is

This is exactly the wrong thing to do. If you do it this way, the CVS-orig directory and its files WILL be imported into your repository. Here's some example output; note that it imports CVS-orig

sahp6613% cvs -d:ext:<my_server>:/cvsroot/playground import test A B
N test/Main.C
I test/.#PPID.16642
cvs import: Importing /cvsroot/playground/test/CVS-orig
N test/CVS-orig/Root
N test/CVS-orig/Repository
N test/CVS-orig/Entries
N test/CVS-orig/Template

The 'cvs import' command ignores a number of files and sub-directories, including any CVS sub-directories in your working directory. So, you can check out a hierarchy from one repository and then immediately import it into another one without removing anything. Only 'real' files will be imported, not the CVS administrative files.

Mark E. Hamilton
Orion International Technologies, Inc.
Sandia National Laboratory, NM.

reply via email to

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