From: "Darrick J. Wong" <djwong@kernel.org>
To: Zorro Lang <zlang@kernel.org>
Cc: fstests@vger.kernel.org, linux-btrfs@vger.kernel.org,
ceph-devel@vger.kernel.org, linux-cifs@vger.kernel.org,
linux-ext4@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net,
linux-fsdevel@vger.kernel.org, linux-nfs@vger.kernel.org,
ocfs2-devel@oss.oracle.com, linux-unionfs@vger.kernel.org,
jack@suse.com, linux-xfs@vger.kernel.org, fdmanana@suse.com,
ebiggers@google.com, brauner@kernel.org, amir73il@gmail.com,
anand.jain@oracle.com
Subject: Re: [PATCH 5/5] fstests/MAINTAINERS: add a co-maintainer for btrfs testing part
Date: Tue, 4 Apr 2023 16:26:16 -0700 [thread overview]
Message-ID: <20230404232616.GE109960@frogsfrogsfrogs> (raw)
In-Reply-To: <20230404171411.699655-6-zlang@kernel.org>
On Wed, Apr 05, 2023 at 01:14:11AM +0800, Zorro Lang wrote:
> Darrick J. Wong would like to nominate Anand Jain to help more on
In case anyone's wondering how this all came about -- Anand asked me how
he could do more upstream fstests review work, so I suggested that he
and I talk to Zorro about delegating some of the review and maintainer
work so that it's not all on Zorro to keep everything running.
> btrfs testing part (tests/btrfs and common/btrfs). He would like to
> be a co-maintainer of btrfs part, will help to review and test
> fstests btrfs related patches, and I might merge from him if there's
> big patchset. So CC him besides send to fstests@ list, when you have
> a btrfs fstests patch.
>
> Signed-off-by: Zorro Lang <zlang@kernel.org>
> ---
>
> Please btrfs list help to review this change, if you agree (or no objection),
> then I'll push this change.
This is what Zorro, Anand, and I sketched out as far as co-maintainer
resposibilities go:
> A co-maintainer will do:
> 1) Review patches are related with him.
> 2) Merge and test patches in his local git repo, and give the patch an ACK.
> 3) Maintainer will trust the ack from co-maintainer more (might merge directly).
> 4) Maintainer might merge from co-maintainer when he has a big patchset wait for
> merging.
>
> Thanks,
> Zorro
>
> MAINTAINERS | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 0ad12a38..9fc6c6b5 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -108,6 +108,7 @@ Maintainers List
> or reviewer or co-maintainer can be in cc list.
>
> BTRFS
> +M: Anand Jain <anand.jain@oracle.com>
I would like to hear agreement from the btrfs community about this
before making this particular change official.
--D
> R: Filipe Manana <fdmanana@suse.com>
> L: linux-btrfs@vger.kernel.org
> S: Supported
> --
> 2.39.2
>
next prev parent reply other threads:[~2023-04-04 23:26 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-04 17:14 [RFC PATCH 0/5] fstests specific MAINTAINERS file Zorro Lang
2023-04-04 17:14 ` [PATCH 1/5] fstests: add MAINTAINERS and get_maintainer.pl files Zorro Lang
2023-04-04 23:21 ` Darrick J. Wong
2023-04-06 20:10 ` John Hubbard
2023-04-04 17:14 ` [PATCH 2/5] tools/get_maintainer.pl: remove penguin chiefs Zorro Lang
2023-04-04 17:14 ` [PATCH 3/5] fstests/MAINTAINERS: add supported mailing list Zorro Lang
2023-04-04 22:16 ` Eric Biggers
2023-04-04 23:22 ` Darrick J. Wong
2023-04-05 14:02 ` Zorro Lang
2023-04-04 23:21 ` Darrick J. Wong
2023-04-05 4:04 ` Steve French
2023-04-05 7:49 ` Christian Brauner
2023-04-05 9:52 ` Jan Kara
2023-04-06 0:25 ` Xiubo Li
2023-04-06 1:53 ` [f2fs-dev] " Chao Yu
2023-04-04 17:14 ` [PATCH 4/5] fstests/MAINTAINERS: add some specific reviewers Zorro Lang
2023-04-04 23:23 ` Darrick J. Wong
2023-04-05 7:47 ` Christian Brauner
2023-04-04 17:14 ` [PATCH 5/5] fstests/MAINTAINERS: add a co-maintainer for btrfs testing part Zorro Lang
2023-04-04 23:26 ` Darrick J. Wong [this message]
2023-04-06 14:17 ` David Sterba
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=20230404232616.GE109960@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=amir73il@gmail.com \
--cc=anand.jain@oracle.com \
--cc=brauner@kernel.org \
--cc=ceph-devel@vger.kernel.org \
--cc=ebiggers@google.com \
--cc=fdmanana@suse.com \
--cc=fstests@vger.kernel.org \
--cc=jack@suse.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=linux-unionfs@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=ocfs2-devel@oss.oracle.com \
--cc=zlang@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