git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Henrik Nilsson <henrik30000@gmail.com>
To: git@vger.kernel.org
Subject: Re: New Bzr to Git migration tool
Date: Thu, 9 Jul 2009 20:06:33 +0000	[thread overview]
Message-ID: <d51232210907091306n46c0cda6g49bf9880d701f2e0@mail.gmail.com> (raw)
In-Reply-To: <37B936CB-2B2F-49DB-B282-EAD6C87E9A63@gmail.com>

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

  reply	other threads:[~2009-07-09 20:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-09 17:36 New Bzr to Git migration tool David Reitter
2009-07-09 20:06 ` Henrik Nilsson [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-07-09 16:59 Henrik Nilsson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=d51232210907091306n46c0cda6g49bf9880d701f2e0@mail.gmail.com \
    --to=henrik30000@gmail.com \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).