cvs2svn does a good job at importing tags and branches. You specify in
the configuration file or on the command line how to setup the
branches and tags, and cvs2svn follows it well.
In fact, what we did was remove lots of the old tags than no longer
made sense. I wrote a Perl script to go through the CVS files removing
these tags. Then, we did the conversion.
What you might want to do is have cvs2svn throw the CVS tags in a
directory like tags/CVS instead of just tags, and then copy over the
tags that you want to keep to the tags directory itself. That way, the
tags directory isn't filled with thousands of tags that mean nothing
to the developers.
We should have done that. That would have been easier than
manipulating the CVS files in the first place.
On Tue, May 19, 2009 at 12:00 PM, Mark-E <meramo@...> 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
> Can anyone provide we with some real life details on how this might have
> worked for them. Thanks!
> We do this, no problem at all.
> View this message in context: http://www.nabble.com/CVS-to-Subversion-Migration-tp23300789p23619284.html > Sent from the Subversion Users mailing list archive at Nabble.com.
> http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2314713 >
> To unsubscribe from this discussion, e-mail: [users-unsubscribe@...].