From: David Chinner <dgc@sgi.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: David Chinner <dgc@sgi.com>, Tim Shimmin <tes@sgi.com>,
xfs-dev@sgi.com, xfs@oss.sgi.com
Subject: Re: review: xfs_growfs_data_private() not logging agf length change
Date: Thu, 7 Jun 2007 22:49:14 +1000 [thread overview]
Message-ID: <20070607124914.GD85884050@sgi.com> (raw)
In-Reply-To: <20070607121853.GA29442@infradead.org>
On Thu, Jun 07, 2007 at 01:18:53PM +0100, Christoph Hellwig wrote:
> On Thu, Jun 07, 2007 at 05:30:34PM +1000, David Chinner wrote:
> > On Thu, Jun 07, 2007 at 05:03:11PM +1000, Tim Shimmin wrote:
> > > Looks like we forgot to log the agf_length change here.
> > >
> > > (cut 'n' pasted patch)
> > >
> > > --Tim
.....
> >
> > Yup, looks ok to me.
>
> Except for the whitespace damage, of course - but that might have been
> the cut & pasting.
The attached patch had no ws damage. ;)
Cheers,
Dave.
--
Dave Chinner
Principal Engineer
SGI Australian Software Group
prev parent reply other threads:[~2007-06-07 12:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-07 7:03 review: xfs_growfs_data_private() not logging agf length change Tim Shimmin
2007-06-07 7:30 ` David Chinner
2007-06-07 12:18 ` Christoph Hellwig
2007-06-07 12:49 ` David Chinner [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=20070607124914.GD85884050@sgi.com \
--to=dgc@sgi.com \
--cc=hch@infradead.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox