From: Dave Chinner <david@fromorbit.com>
To: Theodore Ts'o <tytso@mit.edu>
Cc: xfs@oss.sgi.com, Ext4 Developers List <linux-ext4@vger.kernel.org>
Subject: Re: [PATCH] check: add support for an external test expunging file
Date: Wed, 16 Apr 2014 10:15:30 +1000 [thread overview]
Message-ID: <20140416001530.GU15995@dastard> (raw)
In-Reply-To: <1397530320-20579-1-git-send-email-tytso@mit.edu>
On Mon, Apr 14, 2014 at 10:52:00PM -0400, Theodore Ts'o wrote:
> Currently the -X option is intended to specify a set of expunging
> files which are stored in each test/* subdirectory. As described in
> the commit description for 0b1e8abd4, in order to exclude the test
> generic/280, the -X option is used as follows:
>
> $ cat tests/generic/3.0-stable-avoid
> 280
> $ sudo ./check -X 3.0-stable-avoid generic/280
>
> However, it is sometimes useful to store the set of expunged tests in
> a single file, outside of tests/* subdirectories. This commit allows
> the following:
>
> $ cat /root/conf/data_journal.exclude
> generic/068
> ext4/301
> $ sudo ./check -X /root/conf/data_journal.exclude -g auto
>
> If the argument to the -X option is a pathname (that is, includes a
> '/' character), treat it as the latter case. If it the argument to
> the -X option is just a bare filename (that is, does not include '/'
> character), treat it as the former.
Can you add a new option rather than overloading the existing one
with new meanings and semantics?
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2014-04-16 0:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-15 2:52 [PATCH] check: add support for an external test expunging file Theodore Ts'o
2014-04-16 0:15 ` Dave Chinner [this message]
2014-04-16 0:25 ` Theodore Ts'o
2014-04-16 0:34 ` Dave Chinner
2014-04-16 4:58 ` [PATCH -v2] check: add support for an external file containing tests to exclude Theodore Ts'o
2014-04-16 6:40 ` Dave Chinner
2014-05-12 12:42 ` Theodore Ts'o
2014-05-12 22:00 ` Dave Chinner
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=20140416001530.GU15995@dastard \
--to=david@fromorbit.com \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@mit.edu \
--cc=xfs@oss.sgi.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).