Gesendet: Montag, 12. Juni 2017 um 06:05 Uhr
Von: "Martin Owens" <doctormo@...400...>
An: "Eduard Braun" <Eduard.Braun2@...173...>, ted@...11...
Cc: "Inkscape Devel List" <inkscape-devel@lists.sourceforge.net>
Betreff: Re: [Inkscape-devel] [Gitlab Migration] DONE

Hi Eduard,

So the timeline goes like this:

2003, inscape on svn (I think it was svn)
2006, inkscape moves to bzr, you can see revision 1 on the bzr branch
is MentalGuy 2006, which is what you can see I think in the git
repository.

Exactly, trunk (or now master) starts with the move to bzr in 2006 (as do most other branches)

If you can see 2003 commits, that means ted brought in older commits

from before bzr, which is impressive.

They already were in bzr, see

http://bazaar.launchpad.net/~inkscape.dev/inkscape/RELEASE_0_45_BRANCH/revision/1

http://bazaar.launchpad.net/~inkscape.dev/inkscape/RELEASE_0_46_BRANCH/revision/1

So unless Ted managed to rewrite Bazaar history before importing to git (which would be *really* impressive) it was a legacy from whoever moved the source to bzr back then (probably MenTaLguY)? I don't know why only for 0.45 and 0.46 though...

Will flattening the branch cause hashes to be re-generated?

Yes, if we'd want to do that now we'd have to rewrite basically the whole repository (except the two "magic" branches 0.45/0.46). The only solutions that prevents rewriting commits is the git-replace method I described initially (I already pushed the replacement, but they're not pulled by default so everybody who want's to use it has to create or pull it manually).

I knew from su_v we had previous history also in https://code.launchpad.net/~vcs-imports/inkscape/old-main and I mentioned it a few times to Ted before the migration but I'm afraid he was too busy with everything or did not find it important enough to look into it back then.

Regards,
Eduard