From: Christian Brauner <brauner@kernel.org>
To: Andreas Hindborg <a.hindborg@kernel.org>,
Christoph Hellwig <hch@infradead.org>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
Breno Leitao <leitao@debian.org>,
Joel Becker <jlbec@evilplan.org>
Subject: Re: [PATCH] MAINTAINERS: configfs: add Andreas Hindborg as maintainer
Date: Thu, 3 Apr 2025 13:27:27 +0200 [thread overview]
Message-ID: <20250403-sauer-himmel-df90d0e9047c@brauner> (raw)
In-Reply-To: <87frix5dk3.fsf@kernel.org>
On Fri, Mar 28, 2025 at 05:23:56PM +0100, Andreas Hindborg wrote:
> Hi Christoph,
>
> "Christoph Hellwig" <hch@infradead.org> writes:
>
> > On Wed, Mar 26, 2025 at 05:45:30PM +0100, Andreas Hindborg wrote:
> >> As recommended in plenary session at LSF/MM plenary session on March 25 2025.
> >> Joel is no longer active in the community.
> >
> > I'm not sure who decided that, but that's an exceptionally offensive move.
>
> It was a recommendation given by several people in the plenary session I
> had 10 AM local time on March 25 at LSF. There was agreement in the
> sense that several people recommended this course action and nobody
> objected.
>
> > Joel has helped actually reviewing configfs patches even when I as running
> > the tree, and I explicitly confirmed with him that he is willing to
> > maintain it alone when I dropped the maintainership. You've not even
> > Ced him to tell him about how you force him out of the subsystem he
> > created.
>
> I am deeply sorry for not Cc'ing Joel, that is a mistake. I did not do
> it out of disrespect or ill intent, I simply did not think about it.
> Thank you for correcting this, I appreciate that.
>
> I have sent emails to Joel at least 4 times since the first rust
> configfs series was sent, and I have offered my assistance in
> maintaining configfs if that is the reason of no response.
There's no need to get upset. Several people pointed out that Joel
Becker retired and since he hasn't responded this felt like the right
thing to do. Just send a patch to add him back. I see no reason to not
have Andreas step up to maintain it.
next prev parent reply other threads:[~2025-04-03 11:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-26 16:45 Andreas Hindborg
2025-03-28 9:14 ` Christian Brauner
2025-03-28 11:09 ` Christoph Hellwig
2025-03-28 16:23 ` Andreas Hindborg
2025-04-03 11:27 ` Christian Brauner [this message]
2025-04-04 6:47 ` Christoph Hellwig
2025-04-04 8:42 ` Christian Brauner
2025-04-05 20:29 ` Joel Becker
2025-04-06 9:28 ` Andreas Hindborg
2025-04-22 13:26 ` Andreas Hindborg
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=20250403-sauer-himmel-df90d0e9047c@brauner \
--to=brauner@kernel.org \
--cc=a.hindborg@kernel.org \
--cc=hch@infradead.org \
--cc=jlbec@evilplan.org \
--cc=leitao@debian.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®