From: "Darrick J. Wong" <djwong@kernel.org>
To: Carlos Maiolino <cem@kernel.org>,
Andrey Albershteyn <aalbersh@redhat.com>,
Chandan Babu R <chandanbabu@kernel.org>,
Zorro Lang <zlang@redhat.com>
Cc: xfs <linux-xfs@vger.kernel.org>
Subject: Yearly maintainership rotation?
Date: Tue, 19 Aug 2025 15:54:00 -0700 [thread overview]
Message-ID: <20250819225400.GB7965@frogsfrogsfrogs> (raw)
Hi everyone,
Now that it's nearly September again, what do you all think about
rotating release managers? Chandan has told me that he'd be willing to
step into maintaining upstream xfsprogs; what do the rest of you think
about that?
Also, does anyone want to tackle fstests? :D
--D
next reply other threads:[~2025-08-19 22:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pd4KqICHYbjm5ZYOHBmgSRgs-uKNopGdeI4ARGEXr12t8ZnKctQMdfVRNceZbMeFFKncvIv9_fKyKoMCmCiLfg==@protonmail.internalid>
2025-08-19 22:54 ` Darrick J. Wong [this message]
2025-08-20 8:07 ` Yearly maintainership rotation? Carlos Maiolino
2025-08-20 15:25 ` Darrick J. Wong
2025-08-26 11:23 ` Andrey Albershteyn
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=20250819225400.GB7965@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=aalbersh@redhat.com \
--cc=cem@kernel.org \
--cc=chandanbabu@kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=zlang@redhat.com \
/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