From: Christoph Hellwig <hch@infradead.org>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: Christoph Hellwig <hch@infradead.org>, xfs@oss.sgi.com
Subject: Re: couple small xfstest patches
Date: Mon, 29 Dec 2008 06:37:54 -0500 [thread overview]
Message-ID: <20081229113754.GB10891@infradead.org> (raw)
In-Reply-To: <494FAA58.7070605@sandeen.net>
On Mon, Dec 22, 2008 at 08:55:20AM -0600, Eric Sandeen wrote:
> Christoph Hellwig wrote:
> > On Fri, Nov 21, 2008 at 01:45:23PM -0800, Matthew Kent wrote:
> >> * 189 fails with external devices
> >> * add a unified diff output option, find it easier on the eyes ;)
> >
> > Thanks, I'll put these into my queue. Question to the list: any
> > arguments against just making unified diffs the default for xfsqa
> > output?
>
> none here; I run patched that way already.
Given that no one else complained I'll make it the default.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2008-12-29 11:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-21 21:45 couple small xfstest patches Matthew Kent
2008-11-21 22:17 ` Matthew Kent
2008-12-22 13:08 ` Christoph Hellwig
2008-12-22 14:55 ` Eric Sandeen
2008-12-29 11:37 ` Christoph Hellwig [this message]
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=20081229113754.GB10891@infradead.org \
--to=hch@infradead.org \
--cc=sandeen@sandeen.net \
--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