From: Eryu Guan <eguan@redhat.com>
To: fstests@vger.kernel.org
Subject: Re: [RFD] fstests needs a new maintainer
Date: Tue, 24 May 2016 22:03:01 +0800 [thread overview]
Message-ID: <20160524140301.GU5140@eguan.usersys.redhat.com> (raw)
In-Reply-To: <20160523145503.GA32314@infradead.org>
On Mon, May 23, 2016 at 07:55:03AM -0700, Christoph Hellwig wrote:
> On Mon, May 23, 2016 at 02:41:38PM +0800, Zorro Lang wrote:
> > Thanks for what you did for us. I'm just thinking maybe you can
> > separate fstests maintenance jobs to several different maintainers?
> > Due to fstests project become bigger and bigger, it maybe hard for
> > someone review & merge & verify all kinds of patches.
> >
> > As I know LTP have "not only one" maintainers. I think we still
> > need someone like you can make important decision for fstests.
> > But for some daily jobs, you can distribute them to others.
>
> FYI, back when we team-maintained the xfstests-dev repo together with
> all the other xfs -dev repos it worked out fine. But even with that
> we need someone to volunteer for doing the day to day grunt work.
>
> While I'd be happy to help out I fear I don't have time to do the
> majority of the work at the moment either.
I'd like to help out to do the day to day dirty work as well, though I
don't have such experience before.
Thanks,
Eryu
next prev parent reply other threads:[~2016-05-24 14:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-23 4:53 [RFD] fstests needs a new maintainer Dave Chinner
2016-05-23 6:41 ` Zorro Lang
2016-05-23 14:55 ` Christoph Hellwig
2016-05-23 14:58 ` Eric Sandeen
2016-05-24 14:03 ` Eryu Guan [this message]
2016-05-31 21:12 ` Dave Chinner
2016-06-01 7:00 ` Eryu Guan
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=20160524140301.GU5140@eguan.usersys.redhat.com \
--to=eguan@redhat.com \
--cc=fstests@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