Return-path: Received: from mail-iw0-f174.google.com ([209.85.214.174]:63894 "EHLO mail-iw0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755211Ab0JZUwt convert rfc822-to-8bit (ORCPT ); Tue, 26 Oct 2010 16:52:49 -0400 MIME-Version: 1.0 In-Reply-To: <20101026204043.GA2608@sig21.net> References: <20101025190358.AEC6840F97@repository3.orbit-lab.org> <20101026123552.GA4604@sig21.net> <20101026184123.GA1616@sig21.net> <20101026204043.GA2608@sig21.net> From: "Luis R. Rodriguez" Date: Tue, 26 Oct 2010 13:52:26 -0700 Message-ID: Subject: Re: Compat-wireless release for 2010-10-25 is baked To: Johannes Stezenbach Cc: Ivo Van Doorn , linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org Content-Type: text/plain; charset=UTF-8 Sender: linux-wireless-owner@vger.kernel.org List-ID: On Tue, Oct 26, 2010 at 1:40 PM, Johannes Stezenbach 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