From: "John W. Linville" <linville@tuxdriver.com>
To: linux-wireless@vger.kernel.org
Subject: wireless GIT state...
Date: Thu, 21 Oct 2010 13:57:42 -0400 [thread overview]
Message-ID: <20101021175741.GC6430@tuxdriver.com> (raw)
Hopefully you saw davem's similarly titled post...
I don't see much in the -next patches I've had in wireless-testing
over the last few days that is a big deal for 2.6.37. Those that do
seem important are fixes that can still go anyway.
Stephen usually asks not to have anything in the trees during the
merge window that isn't intended for Linus. So I'm going to reset
wireless-next-2.6 back to where it was for the last pull done by davem.
I will also remove those patches from wireless-testing just to avoid
being out of sync -- the fixes will be back soon, and the others will
be back after the close of the merge window. I will be merging the
fixes and sending them to davem during the window -- feel free to
identify anything you think I might miss.
Also, as I have mentioned previously, I intend to start rebasing
wireless-testing after each merge window. As it stands today, the
history is too much of a mess to be useful for bisection anyway. I
hope everyone can handle a once-per-release rebase of wireless-testing.
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:[~2010-10-21 18:00 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=20101021175741.GC6430@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).