I think metaedit should do nothing if the commit message is not changed.
This would be the same behavior like amend.
___
Evolve-testers mailing list
Evolve-testers@mercurial-scm.org
https://www.mercurial-scm.org/mailman/listinfo/evolve-testers
On Sat, Apr 27, 2019 at 06:13:21PM +0530, Faheem Mitha wrote:
> On Sat, 27 Apr 2019, Friedrich Hagedorn wrote:
>
> > OK, maybe a compromise would be to combine only
> >
> >hg metaedit -r ...
> >hg evolve -aA
> >
> > into metaedit. In this way you can just use metaedit without to know the
>
On Sat, 27 Apr 2019 06:56:03 -0400, Friedrich Hagedorn
wrote:
On Sat, Apr 27, 2019 at 02:37:02PM +0530, Faheem Mitha wrote:
On Sat, 27 Apr 2019, Friedrich Hagedorn wrote:
[...]
> recent commits. In order to metaedit the changesets with branched
> ancestors together with an unclean work
On Sat, Apr 27, 2019 at 02:37:02PM +0530, Faheem Mitha wrote:
> On Sat, 27 Apr 2019, Friedrich Hagedorn wrote:
[...]
> > recent commits. In order to metaedit the changesets with branched
> > ancestors together with an unclean work directory I need to do the
> > following steps:
> >
> >hg
On Sat, 27 Apr 2019, Friedrich Hagedorn wrote:
Hello,
I tried the metaedit command from the evolve extension and was happy to
find a nearly convenient way to refactor the commit messages of my
recent commits. In order to metaedit the changesets with branched
ancestors together with an unclean
Hello,
I tried the metaedit command from the evolve extension and was happy to
find a nearly convenient way to refactor the commit messages of my
recent commits. In order to metaedit the changesets with branched
ancestors together with an unclean work directory I need to do the
following steps:
