From: Ian Clatworthy <ian.clatworthy@canonical•com>
To: Alex Bennee <kernel-hacker@bennee•com>
Cc: Sverre Rabbelier <srabbelier@gmail•com>,
David Reitter <david.reitter@gmail•com>,
vcs-fast-import-devs@lists•launchpad.net, git@vger•kernel.org
Subject: Re: [Vcs-fast-import-devs] bzr to git syncing
Date: Mon, 31 Aug 2009 17:49:43 +1000 [thread overview]
Message-ID: <4A9B8097.4050702@canonical.com> (raw)
In-Reply-To: <fabb9a1e0908281049t64f06a2r5efa114c7bcdc468@mail.gmail.com>
Sverre Rabbelier wrote:
> Heya,
>
> [+vcs-fast-import-devs]
>
> On Fri, Aug 28, 2009 at 10:47, Alex Bennee<kernel-hacker@bennee•com> wrote:
>> 2009/8/28 Sverre Rabbelier <srabbelier@gmail•com>:
>>> 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.
> This seems like a fine case for the new 'feature' command on bzr's export side.
Hmm - I only added that 040000 stuff late last week and it *should* only
be output if you explicitly ask for extended metadata from bzr
fast-export via the --no-plain option? If that's not the case, please
raise a bug here: https://bugs.launchpad.net/bzr-fastimport.
Ian C.
prev parent reply other threads:[~2009-08-31 8:05 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
2009-08-28 17:49 ` Sverre Rabbelier
2009-08-31 7:49 ` Ian Clatworthy [this message]
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=4A9B8097.4050702@canonical.com \
--to=ian.clatworthy@canonical$(echo .)com \
--cc=david.reitter@gmail$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=kernel-hacker@bennee$(echo .)com \
--cc=srabbelier@gmail$(echo .)com \
--cc=vcs-fast-import-devs@lists$(echo .)launchpad.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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