From: Dave Chinner <david@fromorbit.com>
To: "Theodore Ts'o" <tytso@mit.edu>
Cc: Rich Johnston <rjohnston@sgi.com>, xfs-oss <xfs@oss.sgi.com>,
linux-ext4@vger.kernel.org,
linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: Announce re-factor all current xfstests patches request
Date: Thu, 28 Mar 2013 11:35:47 +1100 [thread overview]
Message-ID: <20130328003547.GX6369@dastard> (raw)
In-Reply-To: <20130327214804.GA28143@thunk.org>
On Wed, Mar 27, 2013 at 05:48:04PM -0400, Theodore Ts'o wrote:
> On Thu, Mar 28, 2013 at 07:54:07AM +1100, Dave Chinner wrote:
> >
> > Support for named tests have not yet been added. From the check
> > script:
> >
> > SUPPORTED_TESTS="[0-9][0-9][0-9] [0-9][0-9][0-9][0-9]"
>
> Ah, I thought support for named tests was there. For right now,
> though, if we have test ext4/123 and btrfs/123, that's OK and they are
> considered separate tests, right? Or do we still need to keep the
> numbers unique for now?
Test numbers within a subdir are unique. So yes, ext4/123 and
btrfs/123 are recognised as different tests.
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
WARNING: multiple messages have this Message-ID (diff)
From: Dave Chinner <david@fromorbit.com>
To: Theodore Ts'o <tytso@mit.edu>
Cc: linux-ext4@vger.kernel.org, Rich Johnston <rjohnston@sgi.com>,
linux-btrfs <linux-btrfs@vger.kernel.org>,
xfs-oss <xfs@oss.sgi.com>
Subject: Re: Announce re-factor all current xfstests patches request
Date: Thu, 28 Mar 2013 11:35:47 +1100 [thread overview]
Message-ID: <20130328003547.GX6369@dastard> (raw)
In-Reply-To: <20130327214804.GA28143@thunk.org>
On Wed, Mar 27, 2013 at 05:48:04PM -0400, Theodore Ts'o wrote:
> On Thu, Mar 28, 2013 at 07:54:07AM +1100, Dave Chinner wrote:
> >
> > Support for named tests have not yet been added. From the check
> > script:
> >
> > SUPPORTED_TESTS="[0-9][0-9][0-9] [0-9][0-9][0-9][0-9]"
>
> Ah, I thought support for named tests was there. For right now,
> though, if we have test ext4/123 and btrfs/123, that's OK and they are
> considered separate tests, right? Or do we still need to keep the
> numbers unique for now?
Test numbers within a subdir are unique. So yes, ext4/123 and
btrfs/123 are recognised as different tests.
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-03-28 0:35 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-27 13:23 Announce re-factor all current xfstests patches request Rich Johnston
2013-03-27 13:23 ` Rich Johnston
2013-03-27 13:46 ` Theodore Ts'o
2013-03-27 13:46 ` Theodore Ts'o
2013-03-27 16:42 ` Rich Johnston
2013-03-27 16:42 ` Rich Johnston
2013-03-27 19:05 ` Theodore Ts'o
2013-03-27 19:05 ` Theodore Ts'o
2013-03-27 20:42 ` Zach Brown
2013-03-27 20:42 ` Zach Brown
2013-03-27 20:52 ` Ben Myers
2013-03-27 20:52 ` Ben Myers
2013-03-28 0:34 ` Dave Chinner
2013-03-28 0:34 ` Dave Chinner
2013-03-27 21:02 ` Dave Chinner
2013-03-27 21:02 ` Dave Chinner
2013-03-27 20:54 ` Dave Chinner
2013-03-27 20:54 ` Dave Chinner
2013-03-27 21:48 ` Theodore Ts'o
2013-03-27 21:48 ` Theodore Ts'o
2013-03-28 0:35 ` Dave Chinner [this message]
2013-03-28 0:35 ` 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=20130328003547.GX6369@dastard \
--to=david@fromorbit.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=rjohnston@sgi.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.