From: Chuck Ebbert <76306.1226@compuserve.com>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-netdev <netdev@vger.kernel.org>,
"David S. Miller" <davem@davemloft.net>,
Jeff Garzik <jgarzik@pobox.com>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: -mm -> 2.6.13 merge status (dropped patches?)
Date: Thu, 30 Jun 2005 16:02:51 -0400 [thread overview]
Message-ID: <200506301605_MC3-1-A320-D9D6@compuserve.com> (raw)
On Mon, 20 Jun 2005 at 23:54:58 -0700, Andrew Morton wrote:
> This summarises my current thinking on various patches which are presently
> in -mm. I cover large things and small-but-controversial things. Anything
> which isn't covered here (and that's a lot of material) is probably a "will
> merge", unless it obviously isn't.
What happened to:
remove-last_rx-update-from-loopback-device.patch
It was dropped in 2.6.12-rc1-mm4 with a status of "merged" but it's not
in either 2.6.12 or 2.6.13-rc1.
And in general, who is tracking whether things are being lost?
--
Chuck
next reply other threads:[~2005-06-30 20:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-30 20:02 Chuck Ebbert [this message]
2005-06-30 23:14 ` -mm -> 2.6.13 merge status (dropped patches?) Andrew Morton
2005-07-01 2:52 ` David S. Miller
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=200506301605_MC3-1-A320-D9D6@compuserve.com \
--to=76306.1226@compuserve.com \
--cc=akpm@osdl.org \
--cc=davem@davemloft.net \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).