From: Zach Brown <zach.brown@oracle.com>
To: Nish Aravamudan <nish.aravamudan@gmail.com>
Cc: Michael Halcrow <mhalcrow@us.ibm.com>,
Andrew Morton <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>,
linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] eCryptfs: Delay writing 0's after llseek until write
Date: Tue, 22 May 2007 09:41:08 -0700 [thread overview]
Message-ID: <20070522164108.GV364@mami.zabbo.net> (raw)
In-Reply-To: <29495f1d0705220801v50e53f2dl24f9b198dd31c39c@mail.gmail.com>
> FWIW, I believe Andrew's point was that critical information for Joe
> Enduser (and Joe Patch-Ho) was lacking in the original changelog.
and don't forget Joe eCryptfs-Maintainer-2-Years-In-The-Future.
- z
prev parent reply other threads:[~2007-05-22 16:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-21 23:00 [PATCH] eCryptfs: Delay writing 0's after llseek until write Michael Halcrow
2007-05-22 4:07 ` Andrew Morton
2007-05-22 14:51 ` Michael Halcrow
2007-05-22 15:01 ` Nish Aravamudan
2007-05-22 16:41 ` Zach Brown [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=20070522164108.GV364@mami.zabbo.net \
--to=zach.brown@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhalcrow@us.ibm.com \
--cc=nish.aravamudan@gmail.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