From: "John W. Linville" <linville@tuxdriver.com>
To: linux-wireless@vger.kernel.org
Subject: new stuff for 3.4 needs to be posted _now_
Date: Tue, 8 May 2012 22:39:07 -0400 [thread overview]
Message-ID: <20120509023907.GB2533@tuxdriver.com> (raw)
You may have noticed that Linus has released 3.4-rc6, and "we're
getting close to final 3.4". 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.5. In fact, any non-fix patches need to
already be in wireless-next when the merge window opens if you want
them in 3.5. 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.
You have been warned...this means you!
John
P.S. A combination of personal and business commitments and the
recent kerfuffle regarding bluetooth patches have conspired against my
normal merging duties and habits. I will do what I can to get back
on track, but if Linus does not release an -rc7 then there is a very
good chance that anything not already merged in wireless-next will not
make it for the 3.5 merge window. I apologize for the inconvenience,
but please do plan accordingly.
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
next reply other threads:[~2012-05-09 2:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-09 2:39 John W. Linville [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-03-05 19:05 new stuff for 3.4 needs to be posted _now_ John W. Linville
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=20120509023907.GB2533@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).