netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: Chuck Ebbert <76306.1226@compuserve.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, jgarzik@pobox.com,
	linux-kernel@vger.kernel.org
Subject: Re: -mm -> 2.6.13 merge status (dropped patches?)
Date: Thu, 30 Jun 2005 16:14:56 -0700	[thread overview]
Message-ID: <20050630161456.2ef0ab32.akpm@osdl.org> (raw)
In-Reply-To: <200506301605_MC3-1-A320-D9D6@compuserve.com>

Chuck Ebbert <76306.1226@compuserve.com> wrote:
>
> 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

Davem rejected it.  hm, I can't find the email trail - it was cc'ed to
netdev@oss.sgi.com mid-March, but nothing seems to have been sent back.

> 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?

Things don't get lost.  I have a habit of misremembering the disposition of
patches when preparing -mm release summaries.

  reply	other threads:[~2005-06-30 23:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-30 20:02 -mm -> 2.6.13 merge status (dropped patches?) Chuck Ebbert
2005-06-30 23:14 ` Andrew Morton [this message]
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=20050630161456.2ef0ab32.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=76306.1226@compuserve.com \
    --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).