From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from bh-25.webhostbox.net ([208.91.199.152]:40060 "EHLO bh-25.webhostbox.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751126AbcFGF7f (ORCPT ); Tue, 7 Jun 2016 01:59:35 -0400 Subject: Re: [PATCH 3.10 000/143] 3.10.102-stable review To: Willy Tarreau References: <1465122046-9645-1-git-send-email-w@1wt.eu> <20160607034657.GA8961@roeck-us.net> <20160607040908.GA12457@1wt.eu> <57564DD3.3050601@roeck-us.net> <20160607051718.GB12457@1wt.eu> Cc: linux-kernel@vger.kernel.org, stable@vger.kernel.org From: Guenter Roeck Message-ID: <575662BF.6070809@roeck-us.net> Date: Mon, 6 Jun 2016 22:59:27 -0700 MIME-Version: 1.0 In-Reply-To: <20160607051718.GB12457@1wt.eu> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Sender: stable-owner@vger.kernel.org List-ID: On 06/06/2016 10:17 PM, Willy Tarreau wrote: > On Mon, Jun 06, 2016 at 09:30:11PM -0700, Guenter Roeck wrote: >>>> Do you have a repository, either with the patch >>>> series or with the to-be-tested branch, where the builder could >>>> pick it up ? >>> >>> I don't but I can set something up for you. Would you be OK with a >>> branch in my account (eg: "3.10-for-guenter") which I "git push -f" >>> from my local branch ? That way you always pull from the same branch >>> and we don't care if patches are removed during the process. Just let >>> me know. Otherwise let me know if a different form is desired. >>> >> >> Yes, that would be excellent. I would suggest to name it something like >> stable-3.10-queue, though, to be a bit more generic. After all, other >> testers will want to pick it up as well. > > Well, for me it would not be a "queue" in the sense of how Greg maintains > it but more a release candidate derived from the last 3.10 tag. Basically > if nothing changes between the review and the release, it will just get > an extra commit which is the release tag. If I produce it just for your > use case and you're fine with a force-pushed branch, I'd rather avoid to > confuse other people who probably have no business using it. > Jiri provides a branch for 3.12, exactly as you suggested. In his case it is named stable-3.12-queue. Sasha does the same, with linux-3.18.y-queue and linux-4.1.y-queue. Both force-push as needed. I don't see a problem with it. Other testers such as kernelci.org pick it up from there (or from my repository after I pull it in). In my repository, all branches are named linux-.y.queue; for example, the 3.10 branch in my repository is named linux-3.10.y.queue. Those branches are also force-pushed when updated. Having said that, as long as you make it available, please feel free to name the branch as you like. Thanks, Guenter