On Thu, 18 Jul 2013 07:45:52 +0000, Nico Kadel-Garcia wrote:
...
> * When ready to migrate from the old source control, do a clean dump of the
> old system, and svn import into the new system into a branch, and make a
> locked *tag*. Do not *bother* with the old history.
I strongly disagree with that in that generality. While old history may
be useless to have (and you have it in CC anyway), doing the switch on
a single state is unnecessarily harsh. Instead treat a succession of
states of the 'central' CC branch as a 'vendor branch' and import is
as such into svn. This allows you to continue to run out feature team
branches in CC until all of them have finished while being able to start
new teams on svn beforehand.
While you may not care about *old* history, the history during the
migration is highly helpful. Unless you can afford to do a single shot.
...
> * Under no circumstances maintain parallel work for the same project in
> Subversion and in the old Clearcase, and expect the Subversion history to
> be reconcilable with the parallel Clearcase history
While not trivial this is entirely possible as long as you only want
to sew the two systems together at a single branch (not transferring
the full history, just syncing).
> except by throwing out
> the Subversion repo and starting over from an import.
'Restart from scratch' seems to be a standard svn advice. :-(
(Usually meaning 'do a new checkout'.)
> If I meet one more
> oh-so-clever person who thinks reconciling such things is just a matter of
> a few lines of perl, I will throttle them with their own intestines.
Feel free to come over. I've been doing this for years between CVS and
git with twentyfour lines of shell script and proper procedure (which
is the hard part).
Andreas
--
"Totally trivial. Famous last words."
From: Linus Torvalds <torvalds@*.org>
Date: Fri, 22 Jan 2010 07:29:21 -0800
Received on 2013-07-20 08:17:47 CEST