> Mark-E wrote:
>> Thanks to everyone for their replies. I do have another question concerning
>> We have a lot of tags and branches in our CVS repository and I was wondering
>> when using the cvs2svn script if it will import tags and branches properly.
>> For example, I want to setup the repository in the defaults format of
>> project foo
>> - trunk
>> - branches
>> - tags
>> When I export a project from CVS that has say 10 tags, I would hope that the
>> cvs2svn script will see each tag and build them out properly in the tags
> Yes, I think that is the default. You shouldn't have any surprises from
> the conversion itself, although it might be worth a test run into a
> disposable repo to get started. If you add the converted history to an
> existing repo or combine projects you will break some of subversion's
> date-range operations since they are no longer sequential in respect to
> revision numbers. Also, be aware that tags in subversion are
> conceptually different things (for example you can't float them as in
> cvs) and you may need to change some of your processes to match.
Right. You definitely want to write a little shell script that creates an new
empty svn repos, runs cvs2svn, does the import and checks out the working copy
so you can review it. If you're not happy, modify the shell script, run it
again, rinse until happy.
Don't import your first cvs2svn conversion into your production repository.