ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@linux-foundation.org>
To: Wolfram Sang <wsa@kernel.org>
Cc: ksummit@lists.linux.dev
Subject: Re: [MAINTAINERS SUMMIT] Transparency when rejecting patches without technical reason
Date: Sat, 19 Aug 2023 18:36:29 +0200	[thread overview]
Message-ID: <CAHk-=whAAQi8EtCbaXx6rn63EfrvpeB10fQKqGCH1x8JfdM60g@mail.gmail.com> (raw)
In-Reply-To: <ZODsKnm7B1Q0aPbx@shikoro>

On Sat, 19 Aug 2023 at 18:22, Wolfram Sang <wsa@kernel.org> wrote:
>
> 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.

I don't think there is any value at all in discussing hypotheticals.

But I will say that the next time some has-been superpower ends up
with a premier that goes crazy and starts attacking other countries,
we'll do the same thing.

So that's certainly _one_ reason to not take patches.

But let's hope that one reason ends up never being relevant again, and
as such not really worth discussing (and it's sure as hell not worth
debating).

And other reasons? I don't think most people had "Russia ends up going
rogue, so kernel developers stop taking patches from state-sponsored
actors" on their bingo card in 2021. I certainly didn't.

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.

The Russian situation isn't worth discussing - anybody who wants to
debate it is simply not anybody I want to spend one second debating
*with*.

And any future situation is so hypothetical as to not seemingly be
worth discussing either, unless you have some inside information.

We'll have to take them as they come, and the best we can probably do
is to just hope we don't ever see anything similar in the future.

               Linus

  reply	other threads:[~2023-08-19 16:36 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
2023-08-19 16:36     ` Linus Torvalds [this message]
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='CAHk-=whAAQi8EtCbaXx6rn63EfrvpeB10fQKqGCH1x8JfdM60g@mail.gmail.com' \
    --to=torvalds@linux-foundation.org \
    --cc=ksummit@lists.linux.dev \
    --cc=wsa@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