[Top] [All Lists]

Re: [PATCH 0/3] xfstests patches

To: Dave Chinner <david@xxxxxxxxxxxxx>
Subject: Re: [PATCH 0/3] xfstests patches
From: Rich Johnston <rjohnston@xxxxxxx>
Date: Fri, 15 Mar 2013 08:38:56 -0500
Cc: Eric Sandeen <sandeen@xxxxxxxxxx>, <xfs@xxxxxxxxxxx>
Delivered-to: xfs@xxxxxxxxxxx
In-reply-to: <20130315054350.GC2559@dastard>
References: <1363186623-1378-1-git-send-email-sandeen@xxxxxxxxxx> <514205DC.9040902@xxxxxxx> <20130315054350.GC2559@dastard>
User-agent: Mozilla/5.0 (X11; Linux i686; rv:13.0) Gecko/20120615 Thunderbird/13.0.1
On 03/15/2013 12:43 AM, Dave Chinner wrote:
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

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.


Yes I will, sorry it applied so cleanly and I was trying to get it committed before I left for the day I overlooked the numbering. I will revert and recommit it with the correct number 306. Thanks for pointing that out.


<Prev in Thread] Current Thread [Next in Thread>