From: Wolfram Sang <wsa@kernel.org>
To: ksummit@lists.linux.dev
Subject: [MAINTAINERS SUMMIT] Transparency when rejecting patches without technical reason
Date: Fri, 18 Aug 2023 13:43:57 +0200 [thread overview]
Message-ID: <ZN9ZfUVHrRhd+btc@shikoro> (raw)
[-- Attachment #1: Type: text/plain, Size: 674 bytes --]
Hi all,
this obviously aims at the rejection of networking patches from Baikal
Electronics in March. I only got to know about this yesterday when
reading comments about Debian now supporting the LoongArch architecture.
I admit I thought we accept / reject patches purely because of technical
reasons. If this turns out not to be possible, can we at least agree on
giving detailed reasons then? Like, was it a personal opinion? Was it
because of sanctions? Without reasons as in [1], it makes discussion
harder. And I think we need discussions here to negotiate common
grounds.
With regards,
Wolfram
[1] https://lwn.net/ml/netdev/20230314103316.313e5f61@kernel.org/
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next reply other threads:[~2023-08-18 11:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-18 11:43 Wolfram Sang [this message]
2023-08-18 17:26 ` [MAINTAINERS SUMMIT] Transparency when rejecting patches without technical reason Linus Torvalds
2023-08-19 16:22 ` Wolfram Sang
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=ZN9ZfUVHrRhd+btc@shikoro \
--to=wsa@kernel.org \
--cc=ksummit@lists.linux.dev \
/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).