I've wound up doing a stack of source control migrations to SVN. I may
be in a minority, but in general, *don't*. Do a flat export of the
last timestamped copy, and add them to a Subversion tag in one step.
Lock the tag, and then set a new trunk from that tag. This allows a
number of very useful features:
* Discard old material, especially with passwords or bulky binary
images, before putting it in Subversion. Subversion does not support
clearing out sensitive or inappropriately recorded data.
* Update the layout first to Subversion's trunk, tags, and branches
to create your new workflow.
* Set the svn:eol and svn:keywords consistently at add time.
You can then keep the old ClearCase server around, in read-only mode,
if anyone feels a burning need for the old logs. But for most
projects, preserving that amount of logs in the Subversion repository
itself turns into a lot of engineering time better spent elsewhere.
Note that this is *my* favored approach: others consider the old logs
and layouts and individual merges to be vital and may have better
suggests for keeping it.
On Fri, Nov 15, 2013 at 5:47 PM, Olivier Antoine
oliviera201...@gmail.com wrote:
Hi,
I could not find a tool or an automated way to migrate ClearCase vobs to SVN
repositories. I guess there is not any perfect tool to do this.
I don't think I can use timestamp to build revisions, like for migration cvs
to svn.
On the other hand, the real need is to migrate main to trunk, to migrate the
other branches, probably just for the interesting file/directory versions -
the labelelled ones. I have to migrate the ClearCase labels to SVN tags.
I guess it is not possible to migrate the merge history.
Could you help, please ?
Olivier
