Return-path: Received: from wolverine01.qualcomm.com ([199.106.114.254]:27258 "EHLO wolverine01.qualcomm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752798Ab2GFBHn (ORCPT ); Thu, 5 Jul 2012 21:07:43 -0400 From: Sujith Manoharan MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Message-ID: <20470.14858.754361.629383@gargle.gargle.HOWL> (sfid-20120706_030800_928075_7C4C703A) Date: Fri, 6 Jul 2012 06:36:18 +0530 To: "Luis R. Rodriguez" CC: Sujith Manoharan , "Balasubramanian, Senthil Kumar" , "Manoharan, Rajkumar" , qca-linux-team , Imran Ansari , , , , , , , , , , , , , Subject: Re: 3.5 stable compat-wireless In-Reply-To: <20120705190801.GB11228@tux> References: <20468.35601.132955.802881@gargle.gargle.HOWL> <7A9ADFFA56024346AAE90B6BABC3BD15DD6DEB@NASANEXD02B.na.qualcomm.com> <20469.13787.767293.602337@gargle.gargle.HOWL> <20120705190801.GB11228@tux> Sender: linux-wireless-owner@vger.kernel.org List-ID: Luis R. Rodriguez wrote: > > To make internal releases, I do something like this: > > > > * Maintain a 'linux-foo-pending' branch, add pending patches and kick out releases > > for immediate testing. > > A linux-foo-pending branch of linux-next.git ? No, in compat-wireless - not in upstream, but in my 'forked' tree. This is just to avoid the shuttling of patches between linux-next-pending/ and linux-next-cherry-picks/. Sujith