public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Dave Chinner <david@fromorbit.com>
Cc: xfs@oss.sgi.com
Subject: Re: [PATCH 1/3] xfsqa: clean up 030 repair output
Date: Thu, 29 Apr 2010 06:18:50 -0400	[thread overview]
Message-ID: <20100429101850.GA29677@infradead.org> (raw)
In-Reply-To: <1272500186-29393-2-git-send-email-david@fromorbit.com>

On Thu, Apr 29, 2010 at 10:16:24AM +1000, Dave Chinner wrote:
> With the new checks in xfs_repair, it outputs more information
> about errors found than previously. This new output can be ignored
> for the purpose?? of this test, so filter it all out. This will
> allow the test to run on new and old reapir binaries.

Oh well, I had promised faking up the new output for too long time but
never managed to do it, so let's just put this one in.


Reviewed-by: Christoph Hellwig <hch@lst.de>

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2010-04-29 10:16 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-29  0:16 [PATCH 0/3] xfstests: miscellaneous patches Dave Chinner
2010-04-29  0:16 ` [PATCH 1/3] xfsqa: clean up 030 repair output Dave Chinner
2010-04-29 10:18   ` Christoph Hellwig [this message]
2010-04-29  0:16 ` [PATCH 2/3] xfsqa: keep xfs_fsr output around in test 222 Dave Chinner
2010-04-29 10:19   ` Christoph Hellwig
2010-04-29  0:16 ` [PATCH 3/3] xfsqa: build dbtest on debian platforms Dave Chinner
2010-04-29  6:49   ` Dave Chinner
2010-04-29 10:20     ` Christoph Hellwig
2010-04-29 10:46     ` Christoph Hellwig
2010-04-30  1:26       ` Dave Chinner
2010-04-30  2:28         ` Alex Elder
2010-04-30  3:20           ` Eric Sandeen
2010-04-30  8:55           ` Dave Chinner
2010-04-30 16:39             ` Christoph Hellwig
2010-04-30 17:24               ` Alex Elder
2010-04-29 10:20   ` Christoph Hellwig

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=20100429101850.GA29677@infradead.org \
    --to=hch@infradead.org \
    --cc=david@fromorbit.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