From: "John W. Linville" <linville@tuxdriver.com>
To: linux-wireless@vger.kernel.org
Subject: wireless-testing rebased on top of 3.4-rc2
Date: Mon, 9 Apr 2012 17:06:01 -0400 [thread overview]
Message-ID: <20120409210600.GC26994@tuxdriver.com> (raw)
Greetings,
Just FYI, the wireless-testing tree has been rebased on top of 3.4-rc2.
This tree gets rebased from time to time, particularly after a new
release. It's purpose is just to be a place to integrate and test
current wireless patches on top of a somewhat-recent base from Linus
(usually the latest -rcX). Linus doesn't pull from this tree either
directly or indirectly, so it isn't necessary to preserve its history.
The rebasing does, however, simplify bisections when they become
necessary.
I have also started merging bits for 3.5 in the wireless-next tree
(which feeds wireless-testing). I was at LF's Collaboration Summit
last week, so I am a bit behind on the merging. I hope to catch-up
over the next few days. I apologize for any inconvenience in the
meantime.
Thanks,
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:[~2012-04-09 21:17 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=20120409210600.GC26994@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).