git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: New Bzr to Git migration tool

From
HNHenrik Nilsson <henrik30000@gmail.com>
Date
Jul 9, 2009, 20:06 UTC
Message-ID
<d51232210907091306n46c0cda6g49bf9880d701f2e0@mail.gmail.com>
In-Reply-To
<37B936CB-2B2F-49DB-B282-EAD6C87E9A63@gmail.com>
2009/7/9 David Reitter <david.reitter@gmail.com>:
Show 17 quoted lines
> 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
Previous: David Reitter
Message 2 of 2 in “Re: New Bzr to Git migration tool”
  1. David ReitterJul 9, 2009
  2. Henrik NilssonJul 9, 2009

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.