Understanding the relationship of mercurial and it's extensions

[Uwe Brauer]

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

> Tony Mechelynck <antoine.mechelynck at gmail.com> writes:

>> I'm the one who asked the original question. Ernie seemed (to me)
>> waxing dithyrambic about some third-party "hg-git" extension, so I

> hg-git is pretty good. I’ve been using it for years for large and small
> repositories.

The feature I miss most is the export of named branches or topics as git
branches.

Manuel Jacob provided two changes sets in a separate branch, namely 
6942fb0a8c9d
cd663e6379f0

that I am using since basically 3 years without problems.  Unfortunately
they have never be merged into the default branch.

I understand that importing git branches as named branches it almost
impossible.

Felipe Contreras has a git script that does this, but the
problem is: for git branches there is no reliable «start» of a branch.
There are corner cases, in which 
 git name-rev

Associate a commit with the wrong branch. (You yourself provided such an
example) 

Uwe Bfrauer 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 5673 bytes
Desc: not available
URL: <http://lists.mercurial-scm.org/pipermail/mercurial/attachments/20230830/3c17e014/attachment.p7s>