From: Dave Chinner <david@fromorbit.com>
To: Rich Johnston <rjohnston@sgi.com>
Cc: Eric Sandeen <sandeen@redhat.com>, xfs@oss.sgi.com
Subject: Re: [PATCH 0/3] xfstests patches
Date: Fri, 15 Mar 2013 16:43:50 +1100 [thread overview]
Message-ID: <20130315054350.GC2559@dastard> (raw)
In-Reply-To: <514205DC.9040902@sgi.com>
On Thu, Mar 14, 2013 at 12:16:12PM -0500, Rich Johnston wrote:
> On 03/13/2013 09:57 AM, Eric Sandeen wrote:
> >2 pretty simple ones, and a new btrfs test
> >
> >[PATCH 1/3] xfstests: add 274 to the prealloc group
> >[PATCH 2/3] xfstests: keep newlines out of SCRATCH_DEV_POOL
> >[PATCH 3/3] xfstests: btrfs tests for basic informational commands
> >
> >_______________________________________________
> >xfs mailing list
> >xfs@oss.sgi.com
> >http://oss.sgi.com/mailman/listinfo/xfs
> >
>
> This series has been committed.
Rich, can you please be careful to check the test numbers being used
in patches that are sent to the list before you commit them?
> >[PATCH 3/3] xfstests: btrfs tests for basic informational commands
This test was numbered 313, and so now we have tests 001-306 and 313
in the repository. I noticed that Another of Eric's recent patches
is numbered 315, so it will also need renumbering before commit.
-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-15 5:44 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-13 14:57 [PATCH 0/3] xfstests patches Eric Sandeen
2013-03-13 14:57 ` [PATCH 1/3] xfstests: add 274 to the prealloc group Eric Sandeen
2013-03-13 17:36 ` Rich Johnston
2013-03-13 14:57 ` [PATCH 2/3] xfstests: keep newlines out of SCRATCH_DEV_POOL Eric Sandeen
2013-03-13 17:43 ` Rich Johnston
2013-03-13 17:45 ` Eric Sandeen
2013-03-13 14:57 ` [PATCH 3/3] xfstests: btrfs tests for basic informational commands Eric Sandeen
2013-03-13 15:32 ` Stefan Behrens
2013-03-13 16:17 ` Eric Sandeen
2013-03-13 17:47 ` Rich Johnston
2013-03-13 16:38 ` [PATCH 3/3 V2] " Eric Sandeen
2013-03-13 18:53 ` [PATCH 3/3 V3] " Eric Sandeen
2013-03-13 19:00 ` Stefan Behrens
2013-03-13 19:01 ` [PATCH 3/3 V4] " Eric Sandeen
2013-03-14 13:01 ` Rich Johnston
2013-03-14 13:35 ` Stefan Behrens
2013-03-15 10:16 ` Dave Chinner
2013-03-15 13:46 ` Eric Sandeen
2013-03-15 14:23 ` Rich Johnston
2013-03-15 14:36 ` Eric Sandeen
2013-03-18 13:30 ` Rich Johnston
2013-03-19 14:15 ` Rich Johnston
2013-03-14 17:16 ` [PATCH 0/3] xfstests patches Rich Johnston
2013-03-15 5:43 ` Dave Chinner [this message]
2013-03-15 13:38 ` Rich Johnston
-- strict thread matches above, loose matches on Subject: below --
2011-10-13 0:56 [PATCH 1/3] 263: Functional test case for the btrfs snapshot Dave Chinner
2011-10-18 6:28 ` [PATCH 0/3] xfstests patches Anand Jain
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=20130315054350.GC2559@dastard \
--to=david@fromorbit.com \
--cc=rjohnston@sgi.com \
--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