hg-git plugin, and git-fast export

[Uwe Brauer]

>>> "Arne" == Arne Babenhauserheide <arne_bab at web.de> writes:

    > Am Freitag, 22. Januar 2016, 12:25:15 schrieb Uwe Brauer:
    >> But what's about the hg-git plugin, could it, say, work with some of the
    >> lisp projects which reside in github using that plugin and *not* screw
    >> up things for the other git users? Does anybody has experience with that
    >> plugin used in that way?

    > I’m using hg-git almost daily for contributing to Freenet (on github,
    > sadly). It’s not as convenient as contributing to a hg project (mostly
    > clone, push and pull are quite a bit slower), but it works — and hg
    > with hg-git is easier to use than git.

    > As a hint: Create a bridge repository which is responsible for all
    > interaction with git repos. Then clone your work repository from that.

    > repo-bridge/ ⇔ git
    > repo-work/ ⇔ repo-bridge

    > Just code in the work repo, create bookmarks and push them to the bridge.

That is an excellent idea!

    > hg boo what-git-will-see-as-branch -r REV
    > hg push -B what-git-will-see-as-branch; hg -R ~/repo-bridge push -r what-git-will-see-as-branch

    > and pull

    > hg -R ~/repo-bridge pull; hg pull

    >> The case of collaboration seem less problematic since there branching
    >> and merging does not occur that often.

    > Branching and merging mostly works with hg-git, as long as you keep in
    > mind that git branches are just bookmarks and have no intrinsic
    > meaning.

Right, I have no philosophical reason to favour one of the  other,
however in the hg version I use only named branches are nicely displayed
when using hg log -G while bookmarks are not, that is why I prefer the
former.