how to ammend a changeset and push

Uwe Brauer oub at mat.ucm.es
Mon Nov 18 19:29:20 UTC 2024


> On 18/11/2024 19.30, Uwe Brauer wrote:


> In that case, it sounds like a bug. If the commit still exists in
> Mercurial, you shouldn't get that error. 1.2.0b1 may improve on that,
> though…

Ok but I basically use the hg-git changeset which supports named-branches


> One of the challanges with hg-git is that you have to understand two
> version control systems. Using `--force` with hg-git should be
> equivalent to using `--force-with-lease` with Git, so the push will
> still be rejected if you haven't pulled the latest changes. But it's
> necessary to update any branch in a non-linear fashion, i.e. if you
> modified history.

In my case it was a fork of the MELPA repository, and the maintainer
wanted a series of changes, that should all only be amended. So he
himself did not pushed.

But it is good to know that --force-with-lease is 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. 

-------------- 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/c554be00/attachment.p7s>


More information about the Mercurial mailing list