cvs2svn: Excluding CVS folders

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.

My approach up until this week was to copy the CVS repo, run a 'find
<repodir> -name CVS -type d -exec rm -Rf {} \;' on it, then migrate from
the copy.  We're migrating several dozen repos though, and this gets to be
time and I/O consuming.

So what I did this week was patch cvs2svn to add the option
--exclude-cvs-directories (ctx.exclude_cvs_directories in the options file)
to exclude these from the migration.   So far it works great, although I've
only tested the options file approach since that's all we use.

Is there any interest in me supplying this patch for upstream inclusion in
a future release?  It's a pretty simple set of changes to 3 files:
context.py, repository_walker.py, and cvs2svn-example.options.  I left it
defaulted to off to avoid unexpected behavior changes (although I found it
more unexpected this wasn't default behavior to being with).

David

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

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