Shipping hg-git by default?

[Arne Babenhauserheide]

Am Dienstag, 29. September 2015, 08:27:23 schrieb anatoly techtonik:
> > However, I used it as full-fledged bridge only once, ran into a multitude
> > of problems (different hashes, history rewrite is a PITA, no octopus
> > merges, etc.), and stopped using it that way.
> >
> 
> Different hashes can be a problem when you need to reference revisions, but
> I never faced with this problem until you said it. Probably hg needs to
> mention Git revision number when mirroring remote repo, but it may happen
> that the problem is premature.

I’m facing that problem quite often: I clone some repo, work on it and
push my changes. Then I ask someone “could you check branch X” and he
asks “can you give me the revision number?”

Uh … yes … let me go into .hg/git and do `git log`, using the commit
message to find the right hash.

Or someone tells me that this is fixed “in revision abcxyz”. Uhm…

It would be nice if I could tell hg-git to give me the hg revision
which corresponds to a speciifc git revision — and vice versa. Maybe
even updating to git revisions via -r "git(REV)" or outputting them
with --template "{node|git}\n".

Or get the descriptions in git-tags (I haven’t yet been able to
remember the git command to get them).

But despite all this, using hg to interface with git repos is still
much more convenient for me than using git.

Best wishes,
Arne
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 299 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.mercurial-scm.org/pipermail/mercurial/attachments/20150929/0495be6c/attachment.asc>