From: "John W. Linville" <linville@tuxdriver.com>
To: linux-wireless@vger.kernel.org
Subject: wireless merging -- Re: reminder: bug fixes only
Date: Tue, 3 Aug 2010 10:50:39 -0400 [thread overview]
Message-ID: <20100803145039.GB4779@tuxdriver.com> (raw)
In-Reply-To: <20100802.224837.135539305.davem@davemloft.net>
On Mon, Aug 02, 2010 at 10:48:37PM -0700, David Miller wrote:
>
> 2.6.35 is out, we're about to enter the merge window, so
> if it isn't already in my tree I don't want to see it unless
> it's a bug fix.
In case you missed it, Dave has made the "no more new stuff" call.
Anything that wasn't included in the pull request I sent on Thursday
will not be included in 2.6.36. The exception, of course, is bug
(particularly regression) fixes. If something you have already posted
fits that category, feel free to send me a hint to that effect.
Anything new intended for 2.6.36 should indicate that in the patch
posting.
Generally Stephen requests that nothing be available in the -next
trees during the merge window that isn't being sent to Linus.
The wireless-next-2.6 tree feeds wireless-testing, so you should not
expect to see any post-2.6.36 patches in either of those trees until
the merge window closes in slightly less than two weeks from now.
Fixes will be available as normal.
Thanks for your patience!
John
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
prev parent reply other threads:[~2010-08-03 15:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-03 5:48 reminder: bug fixes only David Miller
2010-08-03 14:50 ` John W. Linville [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=20100803145039.GB4779@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=linux-wireless@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).