Re: [support]: changing author of a commit when rewriting history

Thanks you all. I ended up using hg metaedit. Antonio On 04/12/20 06:03, Manuel Jacob wrote: On 04/12/2020 01.10, Antonio Muci via Mercurial-devel wrote: Hi, sorry for taking over the list, I have a lame support question. I am struggling to find a way to change the author of a commit. I

Re: [support]: changing author of a commit when rewriting history

Thanks for providing a way forward! I'll use that. As a avid user of histedit --interactive, it felt natural to look for author and timestamp editing there. Maybe I'll try to hack a proposal for its inclusion someday. Thanks again. On 04/12/20 01:38, Joerg Sonnenberger wrote: On Fri, Dec

Re: [support]: changing author of a commit when rewriting history

That would be useful for the tip, thanks. I have to to rewrite a commit that is not the last one, like commit 1 in the example. Antonio On 04/12/20 01:23, Joerg Sonnenberger wrote: On Fri, Dec 04, 2020 at 01:10:38AM +0100, Antonio Muci via Mercurial-devel wrote: I am struggling to find

[support]: changing author of a commit when rewriting history

Hi, sorry for taking over the list, I have a lame support question. I am struggling to find a way to change the author of a commit. I do a lot of history rewriting, and "hg histedit --interactive" is invaluable in this regard. Since histedit --interactive does not support changing the author

Re: [PATCH] who: remove OpenJDK

> Il 31/07/2020 17:55 Pierre-Yves David ha > scritto: > > I got int touch with the OpenJDK people one and half year ago. [...] Very active move on your part. Kudos. > Moving to a modern Mercurial version, using sparse revlog for storage > and recomputing delta gave a massive boost to storage

Re: [PATCH] who: remove OpenJDK

That's sad. Apparently OpenJDK started contemplating a migration to git one year ago (2019-07-12): https://openjdk.java.net/jeps/357 I am reporting (an edited version of) the "motivation" section of that ticket, because I'd like a reflection about how mercurial is perceived "out there":

Re: [PATCH 3 of 6] packaging: upgrade Debian packaging to build with Python 3

On 21/10/19 21:52, Augie Fackler wrote: On Mon, Oct 21, 2019 at 09:30:27AM -0700, Martin von Zweigbergk via Mercurial-devel wrote: On Mon, Oct 21, 2019 at 9:21 AM Gregory Szorc wrote: On Mon, Oct 21, 2019 at 6:57 AM Yuya Nishihara wrote: On Mon, 21 Oct 2019 12:00:55 +0200, Denis Laxalde

Re: Is anyone using patchwork?

Just a curiosity: I send my few patches via email (patchbomb ext) because somewhere in the doc it was mentioned as being the preferred method. What is the best way to contribute nowadays? Antonio On May 17, 2019 20:48, Martin von Zweigbergk via Mercurial-devel wrote: > > A few users still

[PATCH] buildrpm: bump bundled Python version to 2.7.16 when building for centos{5, 6}

# HG changeset patch # User Antonio Muci # Date 1555633465 -7200 # Fri Apr 19 02:24:25 2019 +0200 # Branch stable # Node ID 76724fb64a22ca2c68e165e71914827601339300 # Parent 84b5ad5fc2aa81d114d0c8ff869367104e997dd3 buildrpm: bump bundled Python version to 2.7.16 when building for

Re: Making hg 5.0 as beta release with python 3 support.

Hi Matt, Were it under cygwin, running a service would be quite easy using cygrunsrv.exe. Maybe you could see if something equivalent exists for msys.On Mar 5, 2019 15:26, Matt Harbison wrote: > > > On Mar 5, 2019, at 8:25 AM, Pulkit Goyal <7895pul...@gmail.com> wrote: > >> >> >> On Tue, Mar

[PATCH] packaging: fix "make centos{5,6,7}"

# HG changeset patch # User muxator # Date 1539277362 -7200 # Thu Oct 11 19:02:42 2018 +0200 # Node ID 6c5ae5bfae9f44950c041980f446310ea3f96dd3 # Parent 89742f1fa6cbf176259d694377aae17a0f7cd88d packaging: fix "make centos{5,6,7}" Without this change, make centos{5,6,7} fails with error:

[PATCH 5 of 6] packaging: cleanup() did not read the value of $CLEANUP

# HG changeset patch # User muxator # Date 1539116678 -7200 # Tue Oct 09 22:24:38 2018 +0200 # Node ID 4d7d83159122473ab69f9b9c16fab69d10232d78 # Parent 374fcdd01ef6b813d578d865eaccb94d3cda5dc8 packaging: cleanup() did not read the value of $CLEANUP When the original author put CLEANUP in

[PATCH 3 of 6] packaging: blindly factor out trap's cleanup function in builddeb

# HG changeset patch # User muxator # Date 1539116185 -7200 # Tue Oct 09 22:16:25 2018 +0200 # Node ID 186a840796aae2aa48ca5228fc7225779e3e0ee9 # Parent f774dfa1595d4935879d2abbb8b4c802d8af0c65 packaging: blindly factor out trap's cleanup function in builddeb This commit blindly extracts

[PATCH 2 of 6] packaging: print full path to the packages when builddeb finishes successfully

# HG changeset patch # User muxator # Date 1539114049 -7200 # Tue Oct 09 21:40:49 2018 +0200 # Node ID f774dfa1595d4935879d2abbb8b4c802d8af0c65 # Parent 42d6233230fb917da7f53f181f29b4c4c209b65e packaging: print full path to the packages when builddeb finishes successfully diff --git

[PATCH 1 of 6] packaging: print more specific error messages when builddeb fails

# HG changeset patch # User muxator # Date 1539113979 -7200 # Tue Oct 09 21:39:39 2018 +0200 # Node ID 42d6233230fb917da7f53f181f29b4c4c209b65e # Parent a66594c5fad422499bfaf669d182e02fe3c0be32 packaging: print more specific error messages when builddeb fails diff --git

[PATCH 4 of 6] packaging: builddeb's cleanup needs to expand PWD, safely

# HG changeset patch # User muxator # Date 1539116315 -7200 # Tue Oct 09 22:18:35 2018 +0200 # Node ID 374fcdd01ef6b813d578d865eaccb94d3cda5dc8 # Parent 186a840796aae2aa48ca5228fc7225779e3e0ee9 packaging: builddeb's cleanup needs to expand PWD, safely Single quotes would not expand the

[PATCH 6 of 6] packaging: "make deb" no longer fails

# HG changeset patch # User muxator # Date 1539116950 -7200 # Tue Oct 09 22:29:10 2018 +0200 # Node ID 5d892da53728de160568a72a37dda9abcf1f7e9a # Parent 4d7d83159122473ab69f9b9c16fab69d10232d78 packaging: "make deb" no longer fails Release 4.7 rationalized the layout of the build scripts.

Re: [PATCH 1 of 3] makefile: mkdir is not needed on templatized docker builds

robust way of generating packages, but it will take some time. On 15/04/2018 08:59, Anton Shestakov wrote: On Sat, 14 Apr 2018 18:31:24 +0200 Antonio Muci via Mercurial-devel<mercurial-devel@mercurial-scm.org> wrote: # HG changeset patch # User Antonio Muci<a@inwind.it> #

[PATCH 3 of 3] makefile: add Ubuntu Bionic docker targets (.deb and ppa)

# HG changeset patch # User Antonio Muci # Date 1523713197 -7200 # Sat Apr 14 15:39:57 2018 +0200 # Node ID b29e5ecc90eef3af76eaaa4c21b992da66b8e444 # Parent b5874ec21df592d83c3f97aa12ea33dfdb03e839 makefile: add Ubuntu Bionic docker targets (.deb and ppa) Bionic Beaver is

[PATCH 2 of 3] makefile: reformat .PHONY targets

# HG changeset patch # User Antonio Muci # Date 1523723037 -7200 # Sat Apr 14 18:23:57 2018 +0200 # Node ID b5874ec21df592d83c3f97aa12ea33dfdb03e839 # Parent 3c8463e542db60db1ad234ec80f39e290ed17658 makefile: reformat .PHONY targets the list of make targets is likely to

[PATCH 1 of 3] makefile: mkdir is not needed on templatized docker builds

# HG changeset patch # User Antonio Muci # Date 1523714275 -7200 # Sat Apr 14 15:57:55 2018 +0200 # Node ID 3c8463e542db60db1ad234ec80f39e290ed17658 # Parent 1541e1a8e87de9bd6b869ed498ad8e9b93c59d4d makefile: mkdir is not needed on templatized docker builds this imitates

[PATCH 1 of 2] buildrpm: bump bundled python version to 2.7.14 when building for centos{5, 6}

# HG changeset patch # User Antonio Muci # Date 1518476376 -3600 # Mon Feb 12 23:59:36 2018 +0100 # Node ID ae4209858d434d88428c03d3b1be3ec662907ec2 # Parent b62c4154bb287fe0f4c15cdb0d2ef290069288df buildrpm: bump bundled python version to 2.7.14 when building for

[PATCH 2 of 2] buildrpm: bump bundled docutils version to 0.14 when building for centos{5, 6}

# HG changeset patch # User Antonio Muci # Date 1518476745 -3600 # Tue Feb 13 00:05:45 2018 +0100 # Node ID ca93ec462371f185bd737f27fbae73fcca5ad5fa # Parent ae4209858d434d88428c03d3b1be3ec662907ec2 buildrpm: bump bundled docutils version to 0.14 when building for

Re: [PATCH] docker: try to be more adherent to the best practices for writing Dockerfiles

Please ignore this patch. I have just seen that the Fedora Dockerfiles need the same treatment. I will send a single changeset. Sorry for the noise. On 10/01/2017 06:26 PM, a@inwind.it wrote: # HG changeset patch # User muxator # Date 1506812542 -7200 # Sun Oct 01

Re: [PATCH] docker: try to be more adherent to the best practices for writing Dockerfiles

Please ignore also this patch. I have just seen that the Fedora Dockerfiles require the same treatment. I will send a single changeset. On 10/01/2017 06:26 PM, a@inwind.it wrote: # HG changeset patch # User muxator # Date 1506812542 -7200 # Sun Oct 01 01:02:22 2017