From: David Miller <davem@davemloft.net>
To: netdev@vger.kernel.org
Cc: linux-wireless@vger.kernel.org
Subject: decisions, decisions...
Date: Sat, 10 Jan 2009 23:51:41 -0800 (PST) [thread overview]
Message-ID: <20090110.235141.223618374.davem@davemloft.net> (raw)
Ok, the merge window is closed.
So I'm going to rework the net-2.6 tree do that only bug fixes and
-RCx material remains in there. In particular the latest batch
of net_dev_ops conversions are getting pulled out.
I'm going to put those removed changes aside somewhere locally, and I
will not push them into net-next-2.6 until Stephen Rothwell gives the
OK for that kind of stuff showing up in -next.
The merge window was 2 weeks long, so no complaints from anyone
please.
I'm particularly disappointed that I haven't seen one pull request for
wireless pretty much the entire 2 week period. What were you guys
doing, baking gingerbread cookies the entire time? :-))))
next reply other threads:[~2009-01-11 7:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-11 7:51 David Miller [this message]
[not found] ` <20090110.235141.223618374.davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
2009-01-11 7:57 ` decisions, decisions David Miller
2009-01-11 12:14 ` David 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=20090110.235141.223618374.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=linux-wireless@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).