From: Marcel Holtmann <marcel@holtmann.org>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: new stuff for 2.6.36 needs to be posted _now_
Date: Fri, 23 Jul 2010 19:23:01 -0700 [thread overview]
Message-ID: <1279938181.2621.22.camel@localhost.localdomain> (raw)
In-Reply-To: <20100723204529.GE2426@tuxdriver.com>
Hi John,
> You may have noticed that when Linus released 2.6.35-rc6, he
> optimistically predicted that it will be the last -rc for 2.6.35.
> 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 2.6.36. In fact, any non-fix patches need to
> already be in wireless-next-2.6 when the merge window opens if you want
> them in 2.6.36. 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 did see my pull request for bluetooth-next-2.6 tree? I have two
additional patches that should go in, but I wait until you pulled that
one first.
Regards
Marcel
prev parent reply other threads:[~2010-07-24 2:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-23 20:45 new stuff for 2.6.36 needs to be posted _now_ John W. Linville
2010-07-24 2:23 ` Marcel Holtmann [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=1279938181.2621.22.camel@localhost.localdomain \
--to=marcel@holtmann.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
/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).