From: "Stephen C. Tweedie" <sct@redhat.com>
To: "J.A. Magallon" <jamagallon@able.es>
Cc: Lista Linux-Kernel <linux-kernel@vger.kernel.org>,
sct@redhat.com, akpm@zip.com.au, adilger@clusterfs.com
Subject: Re: Latest ext3 merge in mainline lacks 2 hunks ?
Date: Thu, 17 Oct 2002 10:54:39 +0100 [thread overview]
Message-ID: <20021017105439.C3277@redhat.com> (raw)
In-Reply-To: <20021016204648.GA1616@werewolf.able.es>; from jamagallon@able.es on Wed, Oct 16, 2002 at 10:46:48PM +0200
Hi,
On Wed, Oct 16, 2002 at 10:46:48PM +0200, J.A. Magallon wrote:
> I was patching mainline kernels with the ext3 update until this was
> merged recently.
> The merge differs from what I had (taken from LKML) in two missing hunks
> not present still in -pre11.
> Some of the maintainers can say if they are important ?
They are just minor performance-related tweaks that Marcelo wants to
defer merging until 2.4.21-pre opens.
Cheers,
Stephen
prev parent reply other threads:[~2002-10-17 9:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-16 20:46 Latest ext3 merge in mainline lacks 2 hunks ? J.A. Magallon
2002-10-17 9:54 ` Stephen C. Tweedie [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=20021017105439.C3277@redhat.com \
--to=sct@redhat.com \
--cc=adilger@clusterfs.com \
--cc=akpm@zip.com.au \
--cc=jamagallon@able.es \
--cc=linux-kernel@vger.kernel.org \
/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