Anyone tried 1.2.0b1?

[Dan Villiom Podlaski Christiansen]

Hi

Has anyone tested the beta of 1.2? I haven't received much feedback, and
I'd like to know what people think 🙂 In particular w.r.t. the support
for transferring Git SHAs — are the config knobs sensible? Should I
enable it by default?

If I don't hear anything, I'm likely to release it soon. The only
additional change I'm contemplating is dropping Python 3.8, as it's no
longer supported.

- Dan

[Uwe Brauer]

>>> "DVPC" == Dan Villiom Podlaski Christiansen <dan...@gmail.com> writes:

Hi

> Hi
> Has anyone tested the beta of 1.2? I haven't received much feedback,
> and I'd like to know what people think 🙂 In particular w.r.t. the
> support for transferring Git SHAs — are the config knobs sensible?
> Should I enable it by default?

I'd love to test it, but I need for all my git interactions, the branch (and topic support) from the topic: branches-and-stuff.

When will you merge that in?

As I said before, named branches work quite reliable, topics sometime give problems, but I was not able to produce a MWE.

> If I don't hear anything, I'm likely to release it soon. The only
> additional change I'm contemplating is dropping Python 3.8, as it's no
> longer supported.

> - Dan

--
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.

[Ernie Rael]

I've been using it since it was first released. But I'm a lightweight user. No problems, went back and forth with "hggit.usephases" for a few days. Didn't play with any of the other settings.

I should probably turn on hg-git-bundle,hg-git-serve; from what I can tell this would exercise some things even in simple operation. Is there a downside to turning these on?

Noticed that "hg help hggit" doesn't have info on new stuff. I'm guessing that to better understand the new stuff I'd need to better understand git/github. So I guess it's not fair to ask for to much where git would have to be explained;-)

$ hg version -v
Mercurial Distributed SCM (version 6.8.2)
Enabled extensions:

  hggit       external  1.2.0b1 (dulwich 0.22.6)

[Dan Villiom Podlaski Christiansen]

Thanks for the feedback 🙂

Well… the configuration knobs are Mostly Safe™ and therein lies the rub.

If you use the beta and clone a repository with it enabled, you’ll run into a new failure scenario where you may need to pull from Git to push to it. It ought to be handled gracefully, but that’s one possible issue.

The other issue is that the change sets/commits _must_ have been converted to Git prior to pulling them, otherwise you’ll never get the Mercurial to Git mapping. In most cases, that won’t matter, as hg-git is largely bidirectional. But not in all: Some repositories/conversions might just be old, and some might contain commits that can’t be converted without loss of data. Ironically, the hg-git repository itself runs into both of these issues…

(It’s technically possible to synchronise missing commit mappings after the initial transfer, but really hard, I suspect.)

Your point about it not being mentioned in the docs is valid: That’s caused by them being in the `experimental` namespace. I think I’ll move them into `hg-git`. I’d say it’s safe enough to have as a supported feature, even if not enabled by default.

--

- Dan

Den 3. jan. 2025 kl. 19.16 skrev Ernie Rael <err...@raelity.com>:



--
You received this message because you are subscribed to the Google Groups "hg-git" group.
To unsubscribe from this group and stop receiving emails from it, send an email to hg-git+un...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/hg-git/6c39a74d-b861-4382-98fd-777dea018246%40raelity.com.