Rebase commit is not created if it was previously created then pruned

Faheem Mitha faheem at faheem.info
Thu Jul 22 11:59:31 UTC 2021


Hi Christopher,

On Wed, 21 Jul 2021, Christopher Speck wrote:

> I originally posted this in the Mercurial mailing list but found
> there’s a separate one for Evolve.  I’ve come across an issue while
> using the evolve extension where running a `rebase` command
> unexpectedly does not result in a new commit. I’m able to reproduce
> this in a new repository.

> Mercurial: 5.8.1
> Evolve: a65d17b1b463 (stable branch from evolve repo)

[snip]

It you are able to write reproducible scripts, one for each bug, it
would be a good idea to post them on the bug tracker at
https://bz.mercurial-scm.org. You're supposed to select the
"Evolution" keyword. This is what I do. It might be better to use a
version of Evolve with a release number, though I'm not sure if that
is required.

If you cannot reliably reproduce an issue, it probably does not make
sense to report it there.

Regards, Faheem Mitha


More information about the Evolve-testers mailing list