From: Dave Chinner <david@fromorbit.com>
To: Dwight Engen <dwight.engen@oracle.com>
Cc: xfs@oss.sgi.com
Subject: Re: [PATCH] xfstests: fix README, FSTYP options
Date: Wed, 26 Jun 2013 10:50:29 +1000 [thread overview]
Message-ID: <20130626005029.GY29376@dastard> (raw)
In-Reply-To: <20130625153423.513e4074@oracle.com>
On Tue, Jun 25, 2013 at 03:34:23PM -0400, Dwight Engen wrote:
> commit cbcc88fb changed test selection to use shell globs, so fixup the
> examples given in the README file.
>
> add options for FSTYPs supported by _scratch_mkfs().
To tell the truth, I'd prefer to get rid of the -xfs/-udf/... etc
options rather than propoagate them further. We autodetect the FSTYP
just fine on Linux via blkid probing of $TEST_DEV. Hence in reality,
the only CLI option we need is for NFS...
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2013-06-26 0:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-25 19:34 [PATCH] xfstests: fix README, FSTYP options Dwight Engen
2013-06-26 0:50 ` Dave Chinner [this message]
2013-06-26 16:29 ` Dwight Engen
2013-06-27 15:57 ` [PATCH v2] " Dwight Engen
2013-07-09 16:11 ` Ben Myers
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=20130626005029.GY29376@dastard \
--to=david@fromorbit.com \
--cc=dwight.engen@oracle.com \
--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