From: "John W. Linville" <linville@tuxdriver.com>
To: linux-wireless@vger.kernel.org
Subject: wireless-next-2.6 reminder -- [sfr@canb.auug.org.au: linux-next: reminder]
Date: Mon, 1 Mar 2010 09:20:04 -0500 [thread overview]
Message-ID: <20100301142004.GB2961@tuxdriver.com> (raw)
Since wireless-next-2.6 is a feeder tree for linux-next, you can
expect that I will not be adding patches to wireless-next-2.6 until
after 2.6.34-rc1 is released. Since wireless-next-2.6 also feeds
wireless-testing, you can also expect that non-fix patches will not
be added to wireless-testing until that same time.
Thanks for your understanding and cooperation!
John
----- Forwarded message from Stephen Rothwell <sfr@canb.auug.org.au> -----
> Date: Mon, 1 Mar 2010 10:35:34 +1100
> From: Stephen Rothwell <sfr@canb.auug.org.au>
> To: LKML <linux-kernel@vger.kernel.org>
> Cc: linux-next@vger.kernel.org
> Subject: linux-next: reminder
> X-Mailer: Sylpheed 3.0.0 (GTK+ 2.18.7; i486-pc-linux-gnu)
>
> Hi all,
>
> Please do not put stuff destined for v2.6.35 into linux-next until *after*
> Linus' releases v2.6.34-rc1.
>
> Thanks for your cooperation.
>
> --
> Cheers,
> Stephen Rothwell sfr@canb.auug.org.au
> http://www.canb.auug.org.au/~sfr/
----- End forwarded message -----
--
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:[~2010-03-01 14:30 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=20100301142004.GB2961@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).