From: Wolfram Sang <wsa@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: ksummit@lists.linux.dev
Subject: Re: [MAINTAINERS SUMMIT] Transparency when rejecting patches without technical reason
Date: Mon, 21 Aug 2023 21:43:29 +0200 [thread overview]
Message-ID: <ZOO+YZrPNmop8it6@ninjato> (raw)
In-Reply-To: <CAHk-=whAAQi8EtCbaXx6rn63EfrvpeB10fQKqGCH1x8JfdM60g@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 647 bytes --]
> So unless you have a crystal ball and can predict what the next event
> that would cause us to not accept patches would look like, what is
> there to discuss?
>
> That's kind of my point.
First, thank you for these answers. They provide further information I
was initially looking for to get a better understanding of the
situation. I was simply wondering if we couldn't provide such
information right away, but maybe you are right with that it is hardly
forseeable and, thus, managable. It is probably easiest to ask the
involved people directly next time. And I am all with you, I sincerely
hope there will be no next time!
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2023-08-21 19:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-18 11:43 [MAINTAINERS SUMMIT] Transparency when rejecting patches without technical reason Wolfram Sang
2023-08-18 17:26 ` Linus Torvalds
2023-08-19 16:22 ` Wolfram Sang
2023-08-19 16:36 ` Linus Torvalds
2023-08-21 19:43 ` Wolfram Sang [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=ZOO+YZrPNmop8it6@ninjato \
--to=wsa@kernel.org \
--cc=ksummit@lists.linux.dev \
--cc=torvalds@linux-foundation.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).