One more quick thought...
On Wed, Nov 20, 2024 at 12:16 PM Daniel Sahlberg <
daniel.l.sahlb...@gmail.com> wrote:
> Den ons 20 nov. 2024 kl 14:50 skrev Daniel Shahaf >:
>
>> Daniel Sahlberg wrote on Mon, 18 Nov 2024 08:52 +00:00:
>
> (snip)
> B. Would more maintainers use the interactive functio
On Wed, Nov 20, 2024 at 9:22 AM Daniel Shahaf wrote:
>
> Nathan Hartman wrote on Tue, 19 Nov 2024 16:00 +00:00:
> > Looking through the backports stuff in tools/dist, currently it's a
> > little bit messy. I wonder if things can be simplified with a minimal
> > amount of effort.
> >
> > What if we
Den ons 20 nov. 2024 kl 18:15 skrev Daniel Sahlberg <
daniel.l.sahlb...@gmail.com>:
> Missed [backports_tests_p[yl].py], but I'm looking now. It did't work with
> Py3, but I changed a few things in r1921976. It seems a bunch of tests fail
> right now, don't know if it XFails() but isn't marked pro
Den ons 20 nov. 2024 kl 14:50 skrev Daniel Shahaf :
> Daniel Sahlberg wrote on Mon, 18 Nov 2024 08:52 +00:00:
> > backport.pl is a heavy user of "given ... when ..." and given that these
> > constructs will be removed[1] when Perl 5.42 is released (pun intended),
> we
> > need to take some action.
Nathan Hartman wrote on Tue, 19 Nov 2024 16:00 +00:00:
> Looking through the backports stuff in tools/dist, currently it's a
> little bit messy. I wonder if things can be simplified with a minimal
> amount of effort.
>
> What if we had just one script, actually called backport.py, with
> subcommand
Daniel Sahlberg wrote on Mon, 18 Nov 2024 08:52 +00:00:
> backport.pl is a heavy user of "given ... when ..." and given that these
> constructs will be removed[1] when Perl 5.42 is released (pun intended), we
> need to take some action. I'm guessing we have about one year before
> hitting a brick w
6 matches
Mail list logo
