| Message ID | 20230404171411.699655-6-zlang@kernel.org |
|---|---|
| State | New |
| Headers | show |
| Series | fstests specific MAINTAINERS file | expand |
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 >
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 > 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. > > 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> Acked-by: David Sterba <dsterba@suse.com>
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> R: Filipe Manana <fdmanana@suse.com> L: linux-btrfs@vger.kernel.org S: Supported
Darrick J. Wong would like to nominate Anand Jain to help more on 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. 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(+)