Any plans/needs to extend the fast-import format?

[Miklos Vajna]

On Tue, Aug 25, 2009 at 04:17:21PM +1000, Ian Clatworthy <ian.clatworthy at canonical.com> wrote:
> BTW, most Bazaar users would grumble loudly if most commit messages had
> that additional cross-tool metadata tacked on the end. That sort of
> thing may not matter to the git user base but I can promise you it does
> for ours. Different tools appeal to different groups of users - no
> surprises there.

I may misunderstand your problem, but here is an example I see:

Let's say you renamed foo to bar in bzr, then totally rewrote bar, then
committed. So if you export this to git and import it back, you will
loose the rename info (which is in fact a good thing as in case you
totally rewrote the file, it's not a rename, but let's not talk about it
for now).

So the bzr commit was like this:

----
author Au Thor <author>
rename foo bar
rename dir1 dir2

Commit message.
----

Now you export it to git, tracking metadata at the end of commit
messages:

----
author Au Thor <author>

Commit message.

git-bzr: rename foo bar
git-bzr: rename dir1 dir2
----

and now if you import it back, you can just seek for git-bzr lines at
the end of the commit message and parse them, sou you can rebuild the
original commit object without any problem.

So no, bzr users don't see anything in the commit message and yes, the
fast-import format is left untouched.

Is there a problem somewhere? :)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
Url : https://lists.ubuntu.com/archives/bazaar/attachments/20090825/f4ca5d6d/attachment-0002.pgp