From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751811AbcFGFSG (ORCPT ); Tue, 7 Jun 2016 01:18:06 -0400 Received: from wtarreau.pck.nerim.net ([62.212.114.60]:27588 "EHLO 1wt.eu" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751412AbcFGFSE (ORCPT ); Tue, 7 Jun 2016 01:18:04 -0400 Date: Tue, 7 Jun 2016 07:17:18 +0200 From: Willy Tarreau To: Guenter Roeck Cc: linux-kernel@vger.kernel.org, stable@vger.kernel.org Subject: Re: [PATCH 3.10 000/143] 3.10.102-stable review Message-ID: <20160607051718.GB12457@1wt.eu> References: <1465122046-9645-1-git-send-email-w@1wt.eu> <20160607034657.GA8961@roeck-us.net> <20160607040908.GA12457@1wt.eu> <57564DD3.3050601@roeck-us.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <57564DD3.3050601@roeck-us.net> User-Agent: Mutt/1.6.0 (2016-04-01) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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. Thanks, Willy