linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rich Johnston <rjohnston@sgi.com>
To: Eric Sandeen <sandeen@redhat.com>
Cc: Stefan Behrens <sbehrens@giantdisaster.de>,
	<linux-btrfs@vger.kernel.org>, <xfs@oss.sgi.com>
Subject: Re: [PATCH 3/3] xfstests: btrfs tests for basic informational commands
Date: Wed, 13 Mar 2013 12:47:14 -0500	[thread overview]
Message-ID: <5140BBA2.4050600@sgi.com> (raw)
In-Reply-To: <5140A6AA.2010204@redhat.com>

Looks good Eric, but I will wait for Stefan to look at this version to 
make sure all his comments have been addressed, then I will commit this 
series.  Thanks for the patchset.

Regards
--Rich


  reply	other threads:[~2013-03-13 17:46 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1363186623-1378-1-git-send-email-sandeen@redhat.com>
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 [this message]
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

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=5140BBA2.4050600@sgi.com \
    --to=rjohnston@sgi.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=sandeen@redhat.com \
    --cc=sbehrens@giantdisaster.de \
    --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;
as well as URLs for NNTP newsgroup(s).