From: "John W. Linville" <linville@tuxdriver.com>
To: linux-wireless@vger.kernel.org
Subject: new stuff for 3.3 needs to be posted _now_
Date: Mon, 19 Dec 2011 13:49:43 -0500 [thread overview]
Message-ID: <20111219184943.GA31462@tuxdriver.com> (raw)
You may have noticed that Linus has released 3.2-rc6, and doesn't
plan to go beyond -rc7. So, the merge window is around the corner!
For those that need a reminder, the opening of the merge window is a
_deadline_ for new features. Once the merge window opens, only fixes
will be accepted for 3.3. In fact, any non-fix patches need to
already be in wireless-next when the merge window opens if you want
them in 3.3. That means you need to get them posted _now_, so they
can be reviewed and I can find time to merge them before the deadline.
Just for the record, my employer will be shutdown starting on Friday
and through the New Year's celebration. I will probably pay some
attention to my email over that break, but not as much as usual.
I will not go to any great lengths to turn your failure to plan into
my emergency -- sorry.
You have been warned...this means you!
John
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
reply other threads:[~2011-12-19 19:00 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20111219184943.GA31462@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).