From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Lars-Dominik Braun <lars@6xq.net>
Cc: 46848@debbugs.gnu.org, Marius Bakke <marius@gnu.org>
Subject: [bug#46848] [PATCHES] [core-updates] PEP 517 python-build-system
Date: Mon, 28 Feb 2022 17:32:54 -0500 [thread overview]
Message-ID: <878rtusju1.fsf@gmail.com> (raw)
In-Reply-To: <Yh0hr6TPjAX7cowW@noor.fritz.box> (Lars-Dominik Braun's message of "Mon, 28 Feb 2022 20:25:35 +0100")
Hi Lars,
Lars-Dominik Braun <lars@6xq.net> writes:
> Hi Maxim,
>
>> When you judge the branch ready to merge, could you please send a subset
>> of the patches (at least the ones touching the python-build-system
>> directly) to this issue (marked as v2 -- git send-email -v2) so that
>> they can be more easily commented?
>
> as soon as time permits I can do that. Which route do we want to
> take? Replace python-build-system entirely in one big merge or add a
> new one and slowly migrate?
After the Berlin can be rebooted onto its new file system, I expect it
should allow us to keep the build farm much busier than in the past give
us the headroom to experiment with a PEP 517-focused world rebuilding
branch.
I'd aim to have the build system completely replaced; unless your
experience suggests it's going to take multiple weeks to fix iron out
the kinks?
Thanks,
Maxim
next prev parent reply other threads:[~2022-02-28 22:35 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-01 13:43 [bug#46848] [PATCHES] [core-updates] PEP 517 python-build-system Lars-Dominik Braun
2021-05-15 9:31 ` Lars-Dominik Braun
2021-12-13 20:10 ` Lars-Dominik Braun
2022-01-05 14:51 ` Lars-Dominik Braun
2022-01-20 15:41 ` Marius Bakke
2022-01-20 18:43 ` Lars-Dominik Braun
2022-01-20 20:43 ` Marius Bakke
2023-01-11 15:41 ` Maxim Cournoyer
2023-02-10 10:13 ` bug#46848: " Lars-Dominik Braun
2022-02-26 14:10 ` [bug#46848] " Maxim Cournoyer
2022-02-28 19:25 ` Lars-Dominik Braun
2022-02-28 22:32 ` Maxim Cournoyer [this message]
2022-04-24 9:13 ` Lars-Dominik Braun
2022-04-24 9:22 ` Lars-Dominik Braun
2022-01-23 5:29 ` Maxim Cournoyer
2022-01-23 10:21 ` Lars-Dominik Braun
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=878rtusju1.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=46848@debbugs.gnu.org \
--cc=lars@6xq.net \
--cc=marius@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.