From: "John W. Linville" <linville@tuxdriver.com>
To: linux-wireless@vger.kernel.org
Subject: wireless-next-2.6 rebased from b4e69ac670d71b5748dc81e536b2cb103489badd
Date: Thu, 27 Jan 2011 16:09:53 -0500 [thread overview]
Message-ID: <20110127210953.GB2271@tuxdriver.com> (raw)
I rebased wireless-next-2.6 to drop a patch that I should have merged
through the fixes track. I just merged it yesterday, so if you haven't
pulled in the last day or so (i.e. you don't have anything beyond
commit b4e69ac670d71b5748dc81e536b2cb103489badd) you should be fine.
Otherwise, I apologize for the inconvenience to Gustavo, Luca, Wey-yi,
and whomever else might be following wireless-next-2.6 directly.
John
--
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:[~2011-01-27 21:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-27 21:09 John W. Linville [this message]
2011-01-27 21:29 ` wireless-next-2.6 rebased from b4e69ac670d71b5748dc81e536b2cb103489badd Guy, Wey-Yi
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=20110127210953.GB2271@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).