> We definitely want this patch, but we equally want a way to test (not
> just locally) that it keeps working. Maybe we can better coordinate the
> efforts in #hg-evolve.
Will do, thanks!
___
Mercurial-devel mailing list
On Wed, 26 Jun 2019 15:55:50 -0700
"Ludovic Chabant" wrote:
> Should I re-create the patch on the latest evolve stable now? Or will someone
> else do it?
> I'm asking because py3 support is blocking a few things for sourcehut.
> Thanks!
Personally, I thought you all would discuss py3 efforts
Should I re-create the patch on the latest evolve stable now? Or will someone
else do it?
I'm asking because py3 support is blocking a few things for sourcehut.
Thanks!
On Sat, May 25, 2019, at 00:05, Ludovic Chabant wrote:
> > Does this make any existing tests for evolve pass on py3?
>
> The
> Does this make any existing tests for evolve pass on py3?
The evolve extension wasn't even loading in py3 before this patch --
mercurial core would reject it for trying to add unicode strings to the
command table.
> Taking other patches first would mean this patch would be hard to
> apply and
On Fri, 24 May 2019 15:57:53 +
Ludovic Chabant wrote:
> # HG changeset patch
> # User Ludovic Chabant
> # Date 1558677189 0
> # Fri May 24 05:53:09 2019 +
> # Node ID 3af350fa12d4dbf69d5cbbaf5ca679067472f9ee
> # Parent 0b231ea2124baf74fee5e325922a57fb0d89bbe3
> # EXP-Topic py3
>
