From: Mark Brown <broonie@kernel.org>
To: Jonathan Corbet <corbet@lwn.net>
Cc: Javier Martinez Canillas <javier@dowhile0.org>,
workflows@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] docs: submitting-patches: Suggest a longer expected time for responses
Date: Tue, 3 Oct 2023 18:03:02 +0100 [thread overview]
Message-ID: <68a9bc07-07dc-4e97-ae0e-e0b29c808707@sirena.org.uk> (raw)
In-Reply-To: <87y1gjen5d.fsf@meer.lwn.net>
[-- Attachment #1: Type: text/plain, Size: 820 bytes --]
On Tue, Oct 03, 2023 at 09:33:34AM -0600, Jonathan Corbet wrote:
> I was hoping to see some more comments on this; it is a fairly
> significant change in the expectations we put on our reviewers. Oh
> well, I've applied it. I wonder if we should add a note saying to look
> at the maintainer profile for the subsystem in question for more
> specific guidance? Of course, it would be good to have more of those...
It's the sort of thing that's going to vary quite a lot with things like
the point in the release cycle as well (as the existing text already
gestures towards) plus the complexity of the change, I'm not sure that
setting explicit QoS guarantees is going to work out well. The list of
variables gets long and complicated, and the more explicit things are
the more likely someone is to be disappointed.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2023-10-03 17:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-13 14:56 [PATCH] docs: submitting-patches: Suggest a longer expected time for responses Mark Brown
2023-09-14 4:10 ` Javier Martinez Canillas
2023-10-03 15:33 ` Jonathan Corbet
2023-10-03 17:03 ` Mark Brown [this message]
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=68a9bc07-07dc-4e97-ae0e-e0b29c808707@sirena.org.uk \
--to=broonie@kernel.org \
--cc=corbet@lwn.net \
--cc=javier@dowhile0.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=workflows@vger.kernel.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.
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).