From: Amir Goldstein <amir73il@gmail.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: XFS <xfs@oss.sgi.com>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
sergey ivanov <sergey57@gmail.com>
Subject: Re: [PATCH] fix hardcoded reference to /mnt/test in common.attr
Date: Wed, 1 Jun 2011 06:26:03 +0300 [thread overview]
Message-ID: <BANLkTimvXEd-7ZezUt2ZME0HEuNYHASbsg@mail.gmail.com> (raw)
In-Reply-To: <20110531202926.GA17246@infradead.org>
On Tue, May 31, 2011 at 11:29 PM, Christoph Hellwig <hch@infradead.org> wrote:
> Thanks, applied.
>
> (after fixing whitespace damage in the patch)
Sorry about those... I usually get away with copy&paste of a single patch
to gmail.
it works with kernel coding convention of tab indentation and short lines,
but xfstests appear to have some space indentations and long lines,
so it doesn't go that well.
I apologize in advance for the other damaged patch already sent out
(ext4dev FSTYP support)
>
>
prev parent reply other threads:[~2011-06-01 3:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-31 14:21 [PATCH] fix hardcoded reference to /mnt/test in common.attr Amir Goldstein
2011-05-31 20:29 ` Christoph Hellwig
2011-06-01 3:26 ` Amir Goldstein [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=BANLkTimvXEd-7ZezUt2ZME0HEuNYHASbsg@mail.gmail.com \
--to=amir73il@gmail.com \
--cc=hch@infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=sergey57@gmail.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;
as well as URLs for NNTP newsgroup(s).