From: Teemu Likonen <tlikonen@iki.fi>
To: David Reitter <david.reitter@gmail.com>
Cc: Junio C Hamano <gitster@pobox.com>,
git@vger.kernel.org, bazaar@lists.canonical.com
Subject: Re: Importing Bzr revisions
Date: Mon, 23 Mar 2009 16:07:03 +0200 [thread overview]
Message-ID: <87zlfcz62g.fsf@iki.fi> (raw)
In-Reply-To: <03AC7EDA-2A9F-4626-A67B-CE9F2A88FC7D@gmail.com> (David Reitter's message of "Mon\, 23 Mar 2009 09\:27\:24 -0400")
[I'll Cc to Bazaar list too because this subject is half-Git and
half-Bazaar and we may need help from both sides.]
On 2009-03-23 09:27 (-0400), David Reitter wrote:
> I'm just experimenting with "bzr fast-export", which converts to git,
> and it seems to take about 4 minutes for 1000 revisions on our
> (modern) server. That would be around 7 hours for my emacs repository;
> I can't do that daily.
>
> I wonder if there's a way for (bzr) fast-export / (git) fast-import to
> work incrementally, i.e. for selected or most recent revisions.
They can or should work incrementally, and actually I have succesfully
done that. The idea is to use --import-marks and --export-marks options
with "git fast-import" and --marks option with "bzr fast-export.
I noticed some problems with newer versions of "bzr fast-export", though
(since it was converted to a proper Bzr command). It seems to corrupt
the marks file when doing the first incremental export after the initial
export. At least the revisions are not in right order in the marks file
anymore. "git fast-import" can't continue to import from the same
revision where it left last time and it seems to create alternative
history -- or something.
Really I don't know if this is a bug in Bzr or in Git and haven't
figured out how to file a useful bug report.
next prev parent reply other threads:[~2009-03-23 14:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-23 3:33 Importing Bzr revisions David Reitter
2009-03-23 8:06 ` Junio C Hamano
2009-03-23 12:13 ` David Reitter
2009-03-23 13:27 ` David Reitter
2009-03-23 13:55 ` Shawn O. Pearce
2009-03-23 14:07 ` Teemu Likonen [this message]
2009-03-26 3:05 ` David Reitter
2009-03-23 14:18 ` Pieter de Bie
2009-03-23 15:18 ` David Reitter
2009-03-23 20:15 ` Pieter de Bie
2009-03-23 21:00 ` David Reitter
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=87zlfcz62g.fsf@iki.fi \
--to=tlikonen@iki.fi \
--cc=bazaar@lists.canonical.com \
--cc=david.reitter@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.