ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rafael@kernel.org>
To: Greg KH <greg@kroah.com>
Cc: James Bottomley <James.Bottomley@hansenpartnership.com>,
	"Theodore Ts'o" <tytso@mit.edu>,
	 ksummit@lists.linux.dev, linux-fsdevel@vger.kernel.org
Subject: Re: [MAINTAINER SUMMIT] Adding more formality around feature inclusion and ejection
Date: Fri, 22 Aug 2025 14:08:12 +0200	[thread overview]
Message-ID: <CAJZ5v0jnRU9AGHuOMsGdGwYNO6S88X+EN+WM42UtivUs3TykBw@mail.gmail.com> (raw)
In-Reply-To: <2025082202-lankiness-talisman-3803@gregkh>

On Fri, Aug 22, 2025 at 2:03 PM Greg KH <greg@kroah.com> wrote:
>
> On Fri, Aug 22, 2025 at 09:09:04AM +0100, James Bottomley wrote:
> > So what I saw is that as developers exercised this and effectively
> > disengaged unless directly attacked, it pretty much became all on Linus
> > because no-one was left in the chain. This is precisely where I think
> > we could do with an alternative mechanism.
>
> You are implying here that we all just "ran away" and left Linus to hold
> the bag here, which is NOT the case at all.  This specific issue has
> been discussed to death in a lot of different threads, public and
> private with lots of people involved and none of that would have been
> any different had we had some sort of "process document" ahead of time.
>
> So I don't think that attempting to codify the very rare occurrences like
> this is going to really help out much, given that they are all unique to
> their time/place/subsystem based on our past history like this.

I agree.

  reply	other threads:[~2025-08-22 12:08 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-21  8:56 James Bottomley
2025-08-21 16:27 ` Steven Rostedt
2025-08-21 17:44   ` James Bottomley
2025-08-21 19:15     ` Steven Rostedt
2025-08-22  7:59       ` James Bottomley
2025-08-21 19:32   ` Paul Moore
2025-08-22 11:39   ` Mauro Carvalho Chehab
2025-08-22 13:15     ` Matthew Wilcox
2025-08-21 20:34 ` Theodore Ts'o
2025-08-21 20:59   ` Theodore Ts'o
2025-08-21 22:21   ` Matthew Wilcox
2025-08-22 11:29     ` Mauro Carvalho Chehab
2025-08-22  8:09   ` James Bottomley
2025-08-22 12:03     ` Greg KH
2025-08-22 12:08       ` Rafael J. Wysocki [this message]
2025-08-22 12:24       ` Theodore Tso
2025-08-22 15:31         ` James Bottomley
2025-08-22 16:09           ` Theodore Tso
2025-08-25  8:20           ` Mauro Carvalho Chehab
2025-08-25  7:57         ` Mauro Carvalho Chehab
2025-08-22 15:19       ` James Bottomley
2025-08-23  1:03 ` dan.j.williams

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=CAJZ5v0jnRU9AGHuOMsGdGwYNO6S88X+EN+WM42UtivUs3TykBw@mail.gmail.com \
    --to=rafael@kernel.org \
    --cc=James.Bottomley@hansenpartnership.com \
    --cc=greg@kroah.com \
    --cc=ksummit@lists.linux.dev \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=tytso@mit.edu \
    /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