[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [git] migrating a svn repository with several sub-modules
- From: James Blackburn <jamesblackburn@xxxxxxxxx>
- Date: Fri, 2 Sep 2011 14:51:06 +0100
- Delivered-to: email@example.com
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; bh=DITlbowIaKYHPhV83TftG46A9aWfSSUdj6m4CYivy9w=; b=OvbhsmidluOFK7H5jN/Yxbdkw/CpVldLYLLYxOyIVfsmNSvQtoJr3rQSfhpsUAXvMk 8pudRIYL1lIUMdpMlMS4U2sEjZu3qPVLKaNHejZZxk6hjdzu2G4ZBwhR+BJFndAdlHc8 0FxqDF1+vmWL8PFYxWKpv7VJgAF1yhkvuzEC8=
On 2 September 2011 14:44, Andrew Overholt <overholt@xxxxxxxxxx> wrote:
>> Does anyone have experience with migrating a svn repository with this
>> layout to git?
> I did something similar for Linux Tools. It wasn't easy and I couldn't
> figure out a way to automate it. I used something similar to the
> attached script as a starting point. The main merging tool I used was
> this perl module:
AFAICS find git-stitch-repo is the only tool available for doing this.
For simple linear history it does the right thing.
However where the source repos have more than one line of development,
I'm finding that the produced repo doesn't have correctly unified
branches -- i.e. the generated master doesn't contain the changes from
all the stitched together repos.
Andrew, did you verify that all your tags and branch tags were the
same after the conversion as before, and if so how did you get
git-stitch-repo to produce correct output?