Re: cvs2svn: Excluding CVS folders

On 04/18/2013 10:37 PM, David Morris wrote:
> We're using cvs2svn in our migration from CVS to Subversion.  It's
> working great so far, but one thing that bugs me is that it's migrating
> all the 'CVS' folders in the repository.   I could find no way to stop
> this, and was frankly surprised, as these directories should be useless
> in a SVN scenario.  Why does cvs2svn not exclude them automatically, or
> at least provide an option?  Is there a significance to keeping these
> folders in SVN that I'm completely missing?  Some of our larger
> repositories have upwards of 1000 subdirectories, each of which contains
> a CVS directory.  I've searched and find it surprising that there isn't
> more demand for this (I've not found a single question about it).  I
> always assumed CVS didn't check these in either as they are workspace
> control files, but every one of our CVS repositories so far has them
> checked in.

I'm confused.  The "CVS" directories are usually found in a CVS
checked-out working copy, not in the CVS repository itself.  Since
cvs2svn needs to access the repo and not a working copy, it usually
never *sees* any CVS directories.

Why do you have "CVS" directories checked into your repository?

RCS used to store file histories within the working copy; is it possible
that this is an artifact of some strange migration from RCS in the
distant past?

Michael

-- 
Michael Haggerty
[email protected]
http://softwareswirl.blogspot.com/

------------------------------------------------------
http://cvs2svn.tigris.org/ds/viewMessage.do?dsForumId=1670&dsMessageId=3053624

To unsubscribe from this discussion, e-mail: [[email protected]].