New Bzr to Git migration tool

New Bzr to Git migration tool

[Henrik Nilsson]

Hi
I recently wrote a Bzr to Git migration tool and thought I'd share it
with anyone who might be interested.
It's written in shell-script and iterates through the Bzr commits
while adding those changes to a new Git repository.
Usage is to run it from within a Bzr repository. BzrToGit can be found
at http://sortedbits.ath.cx/scripts/bzrtogit.sh

Henrik Nilsson

Re: New Bzr to Git migration tool

[David Reitter]

Henrik Nilsson wrote on git@vger.kernel.org:

> I recently wrote a Bzr to Git migration tool and thought I'd share it
> with anyone who might be interested.
> It's written in shell-script and iterates through the Bzr commits
> while adding those changes to a new Git repository.

This is interesting to me, as my use case will involve extending an  
existing git repository iteratively from the bzr commits.
Looking at the technique, this should be possible that way.

I am missing support for converting all branches of the repository.   
More importantly, don't merges get lost?  All your git side commits  
seem to have a single parent.

Re: New Bzr to Git migration tool

[Henrik Nilsson]

2009/7/9 David Reitter <david.reitter@gmail.com>:
> Henrik Nilsson wrote on git@vger.kernel.org:
>
>> I recently wrote a Bzr to Git migration tool and thought I'd share it
>> with anyone who might be interested.
>> It's written in shell-script and iterates through the Bzr commits
>> while adding those changes to a new Git repository.
>
> This is interesting to me, as my use case will involve extending an existing
> git repository iteratively from the bzr commits.
> Looking at the technique, this should be possible that way.
>
> I am missing support for converting all branches of the repository.  More
> importantly, don't merges get lost?  All your git side commits seem to have
> a single parent.
>
>
>

Yes I suppose they do.
The Bzr repository I was working on when I wrote this script has not
been dealing with any branches.

I should have mentioned that I am not looking for feedback to work
further on this, unless I have any need for it myself, but you are
very welcome to build upon it. :)

Henrik Nilsson