From: "Theodore Tso" <tytso@mit.edu>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: Greg KH <greg@kroah.com>,
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 12:09:18 -0400 [thread overview]
Message-ID: <20250822160918.GA49788@macsyma.lan> (raw)
In-Reply-To: <62aea685546cee80b18cfd7e1ea50b1a590d5edd.camel@HansenPartnership.com>
On Fri, Aug 22, 2025 at 04:31:49PM +0100, James Bottomley wrote:
>
> When did this become about how our current maintainer pull system
> works? I'm certainly not advocating changing it.
...
> Well I did ask for two concrete things, but I can certainly repeat:
>
> On Fri, 2025-08-22 at 09:09 +0100, James Bottomley wrote:
> > I think I'd be happy if we sort out two things
> >
> > 1. That the decision be taken by more than one person rather than
> > abdicating to last man standing
Well, if we keep the current maintainer pull system, then the natural
consequence is that it *is* up to the higher-level maintainer to make
the decision. In the case where we don't have maintainer teams, then
it will be a single person.
So I don't know how to square your request with your assertion that
you don't want to advocate changing how our current maintainer
hierarchy works. Could you clarify your thinking here?
Thanks,
- Ted
next prev parent reply other threads:[~2025-08-22 16:10 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-21 8:56 [MAINTAINER SUMMIT] Adding more formality around feature inclusion and ejection 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
2025-08-22 12:24 ` Theodore Tso
2025-08-22 15:31 ` James Bottomley
2025-08-22 16:09 ` Theodore Tso [this message]
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=20250822160918.GA49788@macsyma.lan \
--to=tytso@mit.edu \
--cc=James.Bottomley@HansenPartnership.com \
--cc=greg@kroah.com \
--cc=ksummit@lists.linux.dev \
--cc=linux-fsdevel@vger.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