From: Christoph Hellwig <hch@infradead.org>
To: Eric Sandeen <sandeen@redhat.com>
Cc: xfs mailing list <xfs@oss.sgi.com>
Subject: Re: [PATCH] xfstests: Make the SCRATCH_DEV optional
Date: Wed, 3 Jun 2009 13:19:04 -0400 [thread overview]
Message-ID: <20090603171904.GA22100@infradead.org> (raw)
In-Reply-To: <4A26AC60.6060401@redhat.com>
On Wed, Jun 03, 2009 at 12:01:20PM -0500, Eric Sandeen wrote:
> Tests will fail gracefully if there is no SCRATCH_DEV defined, so change
>
> the check script to allow it, and update README to reflect this.
>
> This just makes it simpler to set up the tests, at the expense of
> coverage.
>
> Long term it might be nice to allow either SCRATCH_DEV xor TEST_DEV
> to be missing, but for now this is simple.
Looks good,
Reviewed-by: Christoph Hellwig <hch@lst.de>
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2009-06-03 17:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-03 17:01 [PATCH] xfstests: Make the SCRATCH_DEV optional Eric Sandeen
2009-06-03 17:19 ` Christoph Hellwig [this message]
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=20090603171904.GA22100@infradead.org \
--to=hch@infradead.org \
--cc=sandeen@redhat.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