Understanding the relationship of mercurial and it's extensions

[Dr. Arne Babenhauserheide]

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.

> looked in the Mercurial (version 6.5.1) help if there might exist
> something similar built-in. "hg help extensions" mentioned an
> extension named "git" with the word EXPERIMENTAL in capitals next to
> it, so I ran "hg --config extensions.git=   help git" to know more
> about it. What I saw seemed written for the one and only purpose of
> scaring people away. Still, the presence of that extension
> (experimental and not deprecated) seems to indicate that it is
> intended to be made better eventually. One way to do that, if that

From the code it looks like this is in development since 2020, and there
are still some TODOs:
https://repo.mercurial-scm.org/hg/file/tip/hgext/git/TODO.md

And hg-git is under active development:
https://foss.heptapod.net/mercurial/hg-git/-/commits/branch/default

> third-party extension is really so much better, would be to capitalize
> on it and, if possible, bring it inside. A problem might be a possible
> restrictive license, incompatible with the Mercurial license; but I'm
> sure such things can be solved with enough goodwill on both sides.

Relicensing is not a matter of goodwill: it needs permission by all past
and current contributors.

Best wishes,
Arne
-- 
Unpolitisch sein
heißt politisch sein,
ohne es zu merken.
draketo.de
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 1125 bytes
Desc: not available
URL: <http://lists.mercurial-scm.org/pipermail/mercurial/attachments/20230829/eedf48e3/attachment.asc>