* wireless GIT state...
@ 2010-10-21 17:57 John W. Linville
0 siblings, 0 replies; only message in thread
From: John W. Linville @ 2010-10-21 17:57 UTC (permalink / raw)
To: linux-wireless
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.
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2010-10-21 18:00 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2010-10-21 17:57 wireless GIT state John W. Linville
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).