From: "Ludovic Courtès" <ludo@gnu.org>
To: Andreas Enge <andreas@enge.fr>
Cc: Simon Tournier <zimon.toutoune@gmail.com>,
Christopher Baines <mail@cbaines.net>,
guix-devel@gnu.org
Subject: Re: Proposed changes to the commit policy
Date: Mon, 30 Jan 2023 22:40:42 +0100 [thread overview]
Message-ID: <87o7qfya3p.fsf@gnu.org> (raw)
In-Reply-To: <Y9FE3+zLAZ25Xfj/@jurong> (Andreas Enge's message of "Wed, 25 Jan 2023 16:03:59 +0100")
Hi!
My 2¢ on this… As a committer & reviewer, I love that I can just go to
<https://qa.guix.gnu.org/patches>, pick one of the patch series with a
green tick, and have the assurance that the resource-intensive work is
already done. That makes a big difference!
As someone who submits patches, I realize the delay can be off-putting.
For the hwloc upgrade I recently submitted, I got valuable feedback
pointing at actual issues, but that was about a week later. Then I had
to switch contexts again to adjust the patch accordingly.
I guess that, to a large extent, that’s scheduling and resource issue.
Happy to discuss that in the coming days in Brussels!
Ludo’.
next prev parent reply other threads:[~2023-01-30 21:41 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-13 14:10 Proposed changes to the commit policy (#59513) Christopher Baines
2023-01-16 21:47 ` Christopher Baines
2023-01-17 16:35 ` Ludovic Courtès
2023-01-18 11:23 ` Andreas Enge
2023-01-18 11:45 ` Christopher Baines
2023-01-18 16:54 ` Kaelyn
2023-01-22 17:18 ` Andreas Enge
2023-01-23 9:24 ` Simon Tournier
2023-01-24 9:07 ` Attila Lendvai
2023-01-25 15:03 ` Proposed changes to the commit policy Andreas Enge
2023-01-30 21:40 ` Ludovic Courtès [this message]
2023-02-13 11:41 ` Efraim Flashner
2023-01-30 22:03 ` Proposed changes to the commit policy (#59513) Christopher Baines
2023-01-31 11:00 ` Simon Tournier
2023-02-01 13:09 ` Andreas Enge
2023-01-20 11:50 ` Simon Tournier
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87o7qfya3p.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=andreas@enge.fr \
--cc=guix-devel@gnu.org \
--cc=mail@cbaines.net \
--cc=zimon.toutoune@gmail.com \
/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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).