how to ammend a changeset and push

[Uwe Brauer]

>>> "DVPC" == Dan Villiom Podlaski Christiansen <danchr at gmail.com> writes:

> You really should look into the `evolve` extension; not only is it
> pretty awesome in itself, but it also simplifies editing history when
> using hg-git a good deal.


Oh I do use that extension quite intensively mainly because of topics!
The problem I described was also present when I enabled evolve.

> You can also simply enable `obsolete` support locally, I believe; it
> should have the same effect:

>   [experimental]
>   evolution = yes

ok this setting I did not know, thanks


> In the default setup, any history modification consists of adding new
> commits and stripping the old ones. There's nothing telling hg-git of
> this fact, so you have to invoke `hg git-cleanup` after each
> modification.

Ok good to know, but in order to push, I had to use the force option, which make me shudder.


> If you do enable obsolete/evolution though, the old commits will stick
> around, and be shown with the old Git pseudo-tags pointing to them.
> You can then do a force push to update them.

> (Not sure why evolution is still experimental at this point; it's been
> around for years, and seems to work very well in practice ¯\_(ツ)_/¯)

> Or just the short version: Run `hg git-cleanup` prior to pushing.

Ok I will in the future.
-- 
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. 

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 5684 bytes
Desc: not available
URL: <http://lists.mercurial-scm.org/pipermail/mercurial/attachments/20241118/6e00b612/attachment.p7s>