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: Sat, 19 Aug 2023 18:22:02 +0200 [thread overview]
Message-ID: <ZODsKnm7B1Q0aPbx@shikoro> (raw)
In-Reply-To: <CAHk-=wgQKBvXaSNVxy-2Q3KYeTbv-CGSTf3LSV3=O5howAPifA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 802 bytes --]
Hi Linus,
> This wasn't even remotely a gray area. It's not worth discussing.
I hope you understood that my wish for transparency was not about
discussing if the patches should have gone in or not. It is about
discussing or at least stating which reasons we have for not accepting
patches. From the netdev maintainers reply, I couldn't understand if
being "uncomfortable" was because of personal or juristic reasons. As a
result, I was unsure what to do if such patches would have landed in my
subsystem. If it was personal, then I may or may not have a different
opinion, OK. If it was jurisitc, then it might be wise to follow their
expertise. Of course, I could have asked the netdev maintainers. But if
it is written right away, it makes things easier, or so I thought...
Regards,
Wolfram
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-08-19 16:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-18 11:43 Wolfram Sang
2023-08-18 17:26 ` Linus Torvalds
2023-08-19 16:22 ` Wolfram Sang [this message]
2023-08-19 16:36 ` Linus Torvalds
2023-08-21 19:43 ` Wolfram Sang
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=ZODsKnm7B1Q0aPbx@shikoro \
--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