From: Alex Bennee <kernel-hacker@bennee.com>
To: Sverre Rabbelier <srabbelier@gmail.com>
Cc: git@vger.kernel.org, David Reitter <david.reitter@gmail.com>
Subject: Re: bzr to git syncing
Date: Fri, 28 Aug 2009 18:47:44 +0100 [thread overview]
Message-ID: <b2cdc9f30908281047p76c12029u21b100ae6d88fe93@mail.gmail.com> (raw)
In-Reply-To: <fabb9a1e0908280919o412baeb1ka69968a93297ca59@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 862 bytes --]
2009/8/28 Sverre Rabbelier <srabbelier@gmail.com>:
> Heya,
>
> On Fri, Aug 28, 2009 at 09:02, Alex Bennee<kernel-hacker@bennee.com> wrote:
>> I've attached the fast-import crash I'm seeing. Are you seeing the
>> same sort of failure?
>
> The program you used to generate the stream (I assume git-bzr?) is
> generating an invalid mode, git understands '100644', '100755',
> '120000', and '160000'; the mode in the stream, '040000', is not
> something we understand.
Yeah, it seems in bzr land it mean new directory which we don't care
about. The following patch makes it work. Apologies for failure to
inline but Gmail would just corrupt it if I tried.
I also had to patch the ref check code to accept bzr style branch
names but I suspect that patch should be kept out of the repo.
--
Alex, homepage: http://www.bennee.com/~alex/
http://www.half-llama.co.uk
[-- Attachment #2: 0001-Handle-new-directory-commands-from-a-bzr-fast-export.patch --]
[-- Type: application/x-httpd-php, Size: 1071 bytes --]
[-- Attachment #3: 0002-Allow-in-a-branch-name.patch --]
[-- Type: application/x-httpd-php, Size: 1086 bytes --]
next prev parent reply other threads:[~2009-08-28 17:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-29 19:12 bzr to git syncing David Reitter
2009-08-28 16:02 ` Alex Bennee
2009-08-28 16:19 ` Sverre Rabbelier
2009-08-28 17:47 ` Alex Bennee [this message]
2009-08-28 17:49 ` Sverre Rabbelier
2009-08-31 7:49 ` [Vcs-fast-import-devs] " Ian Clatworthy
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=b2cdc9f30908281047p76c12029u21b100ae6d88fe93@mail.gmail.com \
--to=kernel-hacker@bennee.com \
--cc=david.reitter@gmail.com \
--cc=git@vger.kernel.org \
--cc=srabbelier@gmail.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 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).