From: Nathan Scott <nscott@aconex.com>
To: David Chinner <dgc@sgi.com>
Cc: Timothy Shimmin <tes@sgi.com>, xfs-dev <xfs-dev@sgi.com>,
xfs-oss <xfs@oss.sgi.com>
Subject: Re: Review: ensure EOF writes into existing extents update filesize
Date: Tue, 22 May 2007 11:02:59 +1000 [thread overview]
Message-ID: <1179795779.6273.510.camel@edge> (raw)
In-Reply-To: <20070522004414.GL85884050@sgi.com>
On Tue, 2007-05-22 at 10:44 +1000, David Chinner wrote:
> On Mon, May 21, 2007 at 04:34:26PM +1000, Timothy Shimmin wrote:
> I guess I need to ping Christoph and Nathan on this one....
Could you resend the patch to me please? I lost the previous copy
while ruthlessly ploughing through my mail backlog. ;)
cheers.
--
Nathan
next prev parent reply other threads:[~2007-05-22 0:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-20 23:34 Review: ensure EOF writes into existing extents update filesize David Chinner
2007-05-20 23:40 ` Chris Wedgwood
2007-05-20 23:44 ` David Chinner
2007-05-21 6:34 ` Timothy Shimmin
2007-05-22 0:44 ` David Chinner
2007-05-22 1:02 ` Nathan Scott [this message]
2007-05-22 1:03 ` David Chinner
2007-05-22 4:10 ` Nathan Scott
2007-05-22 6:05 ` David Chinner
2007-05-23 0:02 ` David Chinner
2007-05-23 0:15 ` Nathan Scott
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=1179795779.6273.510.camel@edge \
--to=nscott@aconex.com \
--cc=dgc@sgi.com \
--cc=tes@sgi.com \
--cc=xfs-dev@sgi.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.