From: "Theodore Y. Ts'o" <tytso@mit.edu>
To: Eryu Guan <guaneryu@gmail.com>
Cc: Dave Chinner <david@fromorbit.com>, fstests@vger.kernel.org
Subject: Re: [RFC PATCH 0/2] fstests: boiler plate reductions
Date: Sun, 3 Jun 2018 13:55:50 -0400 [thread overview]
Message-ID: <20180603175550.GA1750@thunk.org> (raw)
In-Reply-To: <20180603135107.GK6581@desktop>
On Sun, Jun 03, 2018 at 09:51:07PM +0800, Eryu Guan wrote:
> > Once we have some consensus on how we want to proceed, I'll do the
> > grunt work and co-ordinate with Eryu on minimising the number of
> > times I have to rebase a patchset that is going to touch around 1500
> > files...
>
> How would you like to proceed with a minimum number of rebasing times? I
> think that most rebase work would come from new tests that being added
> during the whole process, I think I could do
The simplest thing to do would be to just drop any conversions where
there is a merge conflict, since if you have 95% using the template,
and 5% that doesn't, it doesn't much matter. Then Dave could do
another pass, and that would probably get the next 95%, etc., and then
we would be close to do.
So I don't think there's any need to suspend adding new tests. If
there are a few new tests that don't use the template at first, it's
really not the end of the world.
Cheers,
- Ted
next prev parent reply other threads:[~2018-06-03 17:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-29 0:47 [RFC PATCH 0/2] fstests: boiler plate reductions Dave Chinner
2018-05-29 0:47 ` [PATCH 1/2] fstests: generic test setup preamble Dave Chinner
2018-06-03 13:53 ` Eryu Guan
2018-06-04 2:58 ` Dave Chinner
2018-05-29 0:47 ` [PATCH 2/2] fstests: start changeover to spdx license tags Dave Chinner
2018-05-29 2:44 ` [RFC PATCH 0/2] fstests: boiler plate reductions Dave Chinner
2018-06-03 13:51 ` Eryu Guan
2018-06-03 17:55 ` Theodore Y. Ts'o [this message]
2018-06-04 2:50 ` Dave Chinner
2018-06-04 3:00 ` Dave Chinner
2018-06-07 5:30 ` Eryu Guan
2018-06-08 6:17 ` 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=20180603175550.GA1750@thunk.org \
--to=tytso@mit.edu \
--cc=david@fromorbit.com \
--cc=fstests@vger.kernel.org \
--cc=guaneryu@gmail.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;
as well as URLs for NNTP newsgroup(s).