From: Christoph Hellwig <hch@infradead.org>
To: Boris Ranto <branto@redhat.com>
Cc: Christoph Hellwig <hch@infradead.org>, xfs@oss.sgi.com
Subject: Re: xfstests: fix 108 through config mechanism
Date: Tue, 14 Dec 2010 14:17:13 -0500 [thread overview]
Message-ID: <20101214191713.GA26513@infradead.org> (raw)
In-Reply-To: <1292338417.3296.57.camel@dhcp-31-190.brq.redhat.com>
On Tue, Dec 14, 2010 at 03:53:37PM +0100, Boris Ranto wrote:
> I didn't like it much either but I found it quite easy to implement with quite high probability of future usage.
>
> I found the following modification sufficient although I'm not sure I put the _filter_spaces in right place (I'd say it's quite universal so it could find a usage in other cases):
This patch looks good to me. Can you resent it in the correct format:
- a descriptive subject
- mail body containing a short explanation, than the signed-off-by
line, then the actual patch.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2010-12-14 19:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-09 14:40 xfstests: fix 108 through config mechanism Boris Ranto
2010-12-10 14:37 ` Christoph Hellwig
2010-12-14 14:53 ` Boris Ranto
2010-12-14 19:17 ` 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=20101214191713.GA26513@infradead.org \
--to=hch@infradead.org \
--cc=branto@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