On Thu, 19 Aug 2021 00:23:26 -0400
Christopher Speck wrote:
> The commit message cannot be modified to include additional noise for the
> case I'm working on. I'm not familiar with extras, but that might be a way
> to work around this. Does that require any further extension to be enabled
>
Hello, thank you for the reply.
The tool I'm working on isn't getting tripped up by additional output but
is getting tripped up in that it's trying to identify the new rebased
commit. It's doing this by retrieving the changeset hash for tip after
running the rebase command. However in this
On Wed, 21 Jul 2021 16:41:56 -0400
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
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
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.
