Long-term planning for hg-git?

[Guy Pardon]

Hi,

With the help of this group and the kind members in it, I have found a way to make hg-git work for me.

Now before we migrate our hg hosting to git(hub): what is the long-term support plan for hg-git?

My coworkers like git, but given that I have done most things in hg I would like to have the option to stay on an hg client for a long time.

Thanks

Guy

[Uwe Brauer]

>>> "GP" == Guy Pardon <dr.guy...@gmail.com> writes:

Hi

Independent of the long term plans (and I have to add, that sadly there
are very few developers for hg-git, right now it seems basically Dan
Villiom Podlaski Christiansen), I have an experience for last 3 or 4
years using hg-git, for some FOSS software, and in some cases I have
write access) and you should think about the following,

1. Are you comfortable with bookmarks? (I am not this is why I chose
hg over git, I want to know precisely to which branch a change
set belongs (git ships name-rev, which only the fly tries to
calculate to which branch a commit belongs, but it sometimes
fails since git has no way to know when a branch started).

2. If not, you can export hg named branches or topics as git
branches. I do always the latter.

3. But git branches get always imported as bookmarks. If there are
few git branches that should not be a problem, but in case there
are many, say in GNU emacs, then things can get complicated.

> Thanks
> Guy

--
I strongly condemn Hamas heinous despicable pogroms/atrocities on Israel
I strongly condemn Putin's war of aggression against Ukraine.
I support to deliver weapons to Ukraine's military.
I support the EU and NATO membership of Ukraine.

[Guy Pardon]

Thanks Uwe :-)

We don't use "branches" (or rarely). Most of our branches are heavy "clones" that we can dispose of in case a merge fails. That's intentional to make things explicit.

So I guess that makes our use case a bit simpler?

Guy

Op maandag 4 maart 2024 om 14:55:22 UTC+1 schreef o...@ucm.es:

[Dan Villiom Podlaski Christiansen]

Well, the only guarantee I can offer is “best effort”… Simply put,
there's no company backing hg-git, and working on it is not part of my
day job, so you won't get any hard warranties of the sort that usually
comes with money changing hands.

That being said, I use it as my daily driver, and have done so for
several years. I don't plan on switching to the Git command line any
time soon.

The worst you can expect is that a new Mercurial release changes
something that hg-git relies on, and I haven't fixed it yet. I do my
best, but I did miss a release not too long ago — but the old release
kept working. In reality, though, you're relying on the efforts of a
single contributor — but perhaps you could offer a bit of help? 🙂
Say, reviews, testing, feedback on merge requests — anything is much
appreciated!

--
Dan Villiom Podlaski Christiansen
dan...@gmail.com

[Uwe Brauer]

I appreciate this very much. Since I still use an old hg-git version
(Manuel Jacobs branch), remind me please what are the minimal python
requirements to run the latest hg-git.


I need to upgrade my distribution....

Once I have done that, I could run tests, but my python knowledges are
not sufficient for providing patches....

> --
> Dan Villiom Podlaski Christiansen
> dan...@gmail.com

[Dan Villiom Podlaski Christiansen]

On 04/03/2024 22.06, Uwe Brauer wrote:

> I appreciate this very much. Since I still use an old hg-git version
> (Manuel Jacobs branch), remind me please what are the minimal python
> requirements to run the latest hg-git.

In general, the newer, the better, but the current minimum requirements are:

* Mercurial 6.1
* Dulwich 0.20.11
* Python 3.8


--

- Dan