On Fri, 2017-06-02 at 01:22 +0200, Eduard Braun wrote:
Am 01.06.2017 um 10:18 schrieb Eduard Braun:
Am 01.06.2017 um 06:51 schrieb Ted Gould:
Sure, I think that'd be helpful. Do you have a patch set somewhere I could try out? I think that if we just put the "LP: #123" in the commit message that'd help a lot.
I'll check it out (probably this evening) and let you know as soon as I have something to test. I just wanted to know if my input was needed/wanted before putting more work in it.
Anything on the other bullet point (bzr revision < 1)? I guess it would be enough to convert revisions < 1 and current trunk to git seperately and then stitch them together as explained at https://stackoverflow.com/questions/1220557/how-do-i-prepend-histor y-to-a-git-repo/1547490#1547490 (probably the grafts + git filter-branch variant as we are still free to "rewrite history").
All right, I just created a fast-export patch, see https://bugs.launchpad.net/inkscape/+bug/1695103
It will create commit messages like
$ git log 48125f06a4fa059ff678284fc104a0b861343acc commit 48125f06a4fa059ff678284fc104a0b861343acc Author: marenhachmann <> Date: Fri May 13 22:04:14 2016 +0200
[Bug #1579939] Ramdom color extension improvements (and new unit test file).
Fixed bugs: - https://launchpad.net/bugs/1579939
Original authors: - marenhachmann - jazzynico <nicoduf@...48...>
(bzr r14884)
(fixed bugs, any additional authors (jazzynico in this example) and the bzr revision would otherwise be lost in the conversion process)
Fields can obviously be adjusted freely...
This is really cool. Thanks Eduard!
I wonder, is there a way to modify the export to export branches as git branches? It's probably a bit extra crazy, but it'd be so nice to have a one shot 'export' that gives you coherent branches instead of separate repositories.
I'm going to think about it, maybe there's a way to automate. Although maybe Ted's managed to sort everything out manually.
Best Regards, Martin Owens