From: Theodore Tso <tytso@mit.edu>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, Mingming Cao <cmm@us.ibm.com>,
Jan Kara <jack@suse.cz>
Subject: Re: linux-next: manual merge of the ext4 tree with the tree
Date: Thu, 26 Feb 2009 09:08:27 -0500 [thread overview]
Message-ID: <20090226140827.GD7227@mit.edu> (raw)
In-Reply-To: <20090226193649.8b240669.sfr@canb.auug.org.au>
On Thu, Feb 26, 2009 at 07:36:49PM +1100, Stephen Rothwell wrote:
> Hi Ted,
>
> On Thu, 26 Feb 2009 01:03:45 -0500 Theodore Tso <tytso@mit.edu> wrote:
> >
> > Thanks, I've moved up the function declaration to avoid the need for a
> > manual fixup.
>
> Thanks.
np! Saves work for you, and it saves work for Linus. :-)
- Ted
next prev parent reply other threads:[~2009-02-26 14:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-25 1:52 linux-next: manual merge of the ext4 tree with the tree Stephen Rothwell
2009-02-25 9:43 ` Jan Kara
2009-02-26 6:03 ` Theodore Tso
2009-02-26 8:36 ` Stephen Rothwell
2009-02-26 14:08 ` Theodore Tso [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-02-27 2:03 Stephen Rothwell
2009-03-03 19:09 ` 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=20090226140827.GD7227@mit.edu \
--to=tytso@mit.edu \
--cc=cmm@us.ibm.com \
--cc=jack@suse.cz \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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).