From: Christoph Hellwig <hch@infradead.org>
To: Chris Mason <chris.mason@oracle.com>
Cc: Christoph Hellwig <hch@infradead.org>,
viro <viro@zeniv.linux.org.uk>, jeffm <jeffm@suse.com>,
jack <jack@suse.cz>,
reiserfs-devel <reiserfs-devel@vger.kernel.org>,
linux-ext4 <linux-ext4@vger.kernel.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: Re: [PATCH 1/2] ext3: make ext3 mount default to barrier=1
Date: Thu, 14 Jul 2011 11:19:09 -0400 [thread overview]
Message-ID: <20110714151909.GA8875@infradead.org> (raw)
In-Reply-To: <1310476587-sup-1581@shiny>
On Tue, Jul 12, 2011 at 09:24:47AM -0400, Chris Mason wrote:
> Excerpts from Christoph Hellwig's message of 2011-07-11 14:25:59 -0400:
> > From: Chris Mason <mason@suse.com>
> >
>
> Thanks for digging this out, you can toss in a sob for me. Probably
> best to give yourself credit in the from:, since you went to all the
> trouble of diving in the vendor kernels.
>
> Then again, if you're using the old email to try and throw Andrew off
> our trail, go for it.
Given that it's trivial one liners, and suse actually had config options
around them that I had to remove I might as well claim the patches as
mine. I'll resend them with my From and Signoff lines.
next prev parent reply other threads:[~2011-07-14 15:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-11 18:25 [PATCH 0/2] always default to issue cache flushes Christoph Hellwig
2011-07-11 18:25 ` [PATCH 1/2] ext3: make ext3 mount default to barrier=1 Christoph Hellwig
2011-07-11 19:17 ` Jan Kara
2011-07-11 19:20 ` Christoph Hellwig
2011-07-11 22:23 ` Ted Ts'o
2011-07-12 0:16 ` Eric Sandeen
2011-07-12 13:24 ` Chris Mason
2011-07-14 15:19 ` Christoph Hellwig [this message]
2011-07-11 18:26 ` [PATCH 2/2] reiserfs: make reiserfs default to barrier=flush Christoph Hellwig
2011-07-11 19:19 ` [PATCH 0/2] always default to issue cache flushes Jan Kara
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=20110714151909.GA8875@infradead.org \
--to=hch@infradead.org \
--cc=chris.mason@oracle.com \
--cc=jack@suse.cz \
--cc=jeffm@suse.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=reiserfs-devel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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).