[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <AANLkTi=f-mx1Sqv6+PB5rmitkNnsWaQazrDfV7UNCp34@mail.gmail.com>
Date: Tue, 26 Oct 2010 13:52:26 -0700
From: "Luis R. Rodriguez" <mcgrof@...il.com>
To: Johannes Stezenbach <js@...21.net>
Cc: Ivo Van Doorn <ivdoorn@...il.com>, linux-wireless@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: Compat-wireless release for 2010-10-25 is baked
On Tue, Oct 26, 2010 at 1:40 PM, Johannes Stezenbach <js@...21.net> wrote:
> Hi,
>
> On Tue, Oct 26, 2010 at 09:48:12PM +0200, Ivo Van Doorn wrote:
>> For rt2x00 development you can choose between rt2x00.git and
>> wireless-testing.git,
>> the trees are usually not that far apart, since smaller patches are pushed quite
>> quickly upstream. (Also rt2x00.git is rebased frequently, while
>> wireless-testing.git rarely
>> is rebased)
>
> Thanks for clarification. I guess I'll start with wireless-testing,
> that sounds a bit more newbie-friendly. I just want to avoid
> searching or reporting bugs which are already fixed, but your description
> sounds like changes are pushed from rt2x00.git to wireless-testing.git
> maybe weekly.
Remember, wireless-testing gets stuff from wireless-next.git sucked in
after wireless-2.6.git bits are pulled in, so really its
wireless-next.git --> linux-next.git as the daily compat-wireless is
based on linux-next.git. The wireless-testing.git tree just lets you
use a stabe RC kernel with the next kernels' 802.11 bits sucked in. So
you will get your patches merged daily on a good
John-Linville-and-Stephen-Rothwell-ate-his-wheaties-day :)
> I was afraid patches would be pushed to wireless-testing.git
> only when it's time to get ready for the next merge window.
Hell no!
Luis
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists