From: Dave Chinner <david@fromorbit.com>
To: Eryu Guan <eguan@redhat.com>
Cc: Qu Wenruo <quwenruo@cn.fujitsu.com>,
linux-btrfs@vger.kernel.org, fstests@vger.kernel.org
Subject: Re: [PATCH] fstests: btrfs: Test send on heavily deduped file
Date: Thu, 21 Jul 2016 09:30:00 +1000 [thread overview]
Message-ID: <20160720233000.GY12670@dastard> (raw)
In-Reply-To: <20160720070100.GU27776@eguan.usersys.redhat.com>
On Wed, Jul 20, 2016 at 03:01:00PM +0800, Eryu Guan wrote:
> For running tests, "./check -g auto -x dangerous" might fit your need.
Yes, that's precisely the way the dangerous group is intended to be
used: as a exclusion filter that gets applied to other test group
definitions.
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2016-07-20 23:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-19 2:44 [PATCH] fstests: btrfs: Test send on heavily deduped file Qu Wenruo
2016-07-19 4:35 ` Eryu Guan
2016-07-19 5:42 ` Qu Wenruo
2016-07-20 7:01 ` Eryu Guan
2016-07-20 7:40 ` Qu Wenruo
2016-07-20 23:37 ` Dave Chinner
2016-07-21 2:05 ` Qu Wenruo
2016-07-21 22:57 ` Dave Chinner
2016-07-20 23:30 ` Dave Chinner [this message]
2016-07-19 5:06 ` Qu Wenruo
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=20160720233000.GY12670@dastard \
--to=david@fromorbit.com \
--cc=eguan@redhat.com \
--cc=fstests@vger.kernel.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=quwenruo@cn.fujitsu.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