From: Felix Lechner via "Development of GNU Guix and the GNU System distribution." <guix-devel@gnu.org>
To: Tomas Volf <~@wolfsden.cz>, guix-devel@gnu.org
Subject: Re: How/where/when to ask for a patch review?
Date: Sat, 06 Jan 2024 19:22:49 -0800 [thread overview]
Message-ID: <87msth6d4m.fsf@lease-up.com> (raw)
In-Reply-To: <ZZl2PvBe-fTnt_kj@ws>
Hi Tomas,
On Sat, Jan 06 2024, Tomas Volf wrote:
> what is the proper channel to ask for a patch review and how long
> should one wait before doing so.
Please don't waste your time waiting. The process of patch review and
acceptance here is erratic. I won't go into reasons; the project
understands the problem and is trying several solutions but I'm not sure
they are working. Please go ahead and maintain your own fork of Guix.
They will take what they want.
> PS: This patch being ignored was the last push I needed to start my personal
> fork
This one? [1]
> I would like to diverge as little as possible.
No chance. I run about a hundred patches on top of stock and build half
of all packages myself (mainly due to a defective eudev in Guix). In
another month, I'll be at two hundred.
Again, they will take what they want. Please don't wait. It's an
unreasonable expectation vis-a-vis the group.
Kind regards
Felix
[1] https://debbugs.gnu.org/cgi/bugreport.cgi?bug=67546
next prev parent reply other threads:[~2024-01-07 3:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-06 15:48 How/where/when to ask for a patch review? Tomas Volf
2024-01-07 3:22 ` Felix Lechner via Development of GNU Guix and the GNU System distribution. [this message]
2024-01-07 9:41 ` Nicolas Goaziou via Development of GNU Guix and the GNU System distribution.
2024-01-09 23:33 ` Ludovic Courtès
2024-01-10 14:17 ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
2024-01-10 16:59 ` Tomas Volf
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=87msth6d4m.fsf@lease-up.com \
--to=guix-devel@gnu.org \
--cc=felix.lechner@lease-up.com \
--cc=~@wolfsden.cz \
/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).