From: "John W. Linville" <linville@tuxdriver.com>
To: linux-wireless@vger.kernel.org
Subject: wireless-testing rebased on 3.9-rc1
Date: Wed, 6 Mar 2013 17:44:01 -0500 [thread overview]
Message-ID: <20130306224401.GA20300@tuxdriver.com> (raw)
Now that the merge window is closed and things are progressing towards
3.9, I have rebased the wireless-testing tree upon 3.9-rc1. It won't
stay clean for long, of course -- it will pull from the wireless and
wireless-next trees continually and will pull from the linux tree
after each -rc release, as usual.
The current head of the tree is commit 12c18c7a3d8f20366424834b20be40f7f3a9e2c2.
Please adjust your development trees accordingly.
John
P.S. Note that this has no effect on trees used to push changes
through me towards Dave and Linus. The wireless and wireless-next
trees have merely been fast-forwarded.
--
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:[~2013-03-06 22:45 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=20130306224401.GA20300@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).