Return-path: Received: from bar.sig21.net ([80.81.252.164]:59537 "EHLO bar.sig21.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754539Ab0JZUkr (ORCPT ); Tue, 26 Oct 2010 16:40:47 -0400 Date: Tue, 26 Oct 2010 22:40:43 +0200 From: Johannes Stezenbach To: Ivo Van Doorn Cc: "Luis R. Rodriguez" , linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: Compat-wireless release for 2010-10-25 is baked Message-ID: <20101026204043.GA2608@sig21.net> References: <20101025190358.AEC6840F97@repository3.orbit-lab.org> <20101026123552.GA4604@sig21.net> <20101026184123.GA1616@sig21.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: Sender: linux-wireless-owner@vger.kernel.org List-ID: 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. I was afraid patches would be pushed to wireless-testing.git only when it's time to get ready for the next merge window. Thanks, Johannes