From mboxrd@z Thu Jan 1 00:00:00 1970 From: Wei Liu Subject: Re: [OSSTEST PATCH 4/4] README.bisection: New consumer-oriented document Date: Tue, 20 Oct 2015 10:20:05 +0100 Message-ID: <20151020092005.GA27732@zion.uk.xensource.com> References: <1445271335-21792-1-git-send-email-ian.jackson@eu.citrix.com> <1445271335-21792-4-git-send-email-ian.jackson@eu.citrix.com> <20151019163527.GP28665@zion.uk.xensource.com> <22053.8077.174953.347128@mariner.uk.xensource.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1ZoT5V-0001k4-AR for xen-devel@lists.xenproject.org; Tue, 20 Oct 2015 09:20:09 +0000 Content-Disposition: inline In-Reply-To: <22053.8077.174953.347128@mariner.uk.xensource.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Ian Jackson Cc: xen-devel@lists.xenproject.org, Wei Liu , Ian Campbell List-Id: xen-devel@lists.xenproject.org On Mon, Oct 19, 2015 at 05:51:25PM +0100, Ian Jackson wrote: > Wei Liu writes ("Re: [OSSTEST PATCH 4/4] README.bisection: New consumer-oriented document"): > > On Mon, Oct 19, 2015 at 05:15:35PM +0100, Ian Jackson wrote: > > > + | url used for fetching the bits > > > + | > > > + ` Identifier indicating the purpose for which the tree > > > + is used. > > > > A tab was inserted here. > > Thanks, will fix. > > > > +Progress Reports > ... > > > +These contain the roughly same information; instead of "complete" they > > > +may say "running", "inconclusive", "unreproducible", etc. > > > > On xen-devel there are only "complete" emails. It might be helpful to > > send "unreproducible" and / or "inconclusive" emails as well? What I'm > > thinking is that it would be helpful to clearly indicate human > > intervention is needed. > > There's quite a lot of these. In principle, around one for each > "REGR" ever mentioned in a main push gate flight report. > > I don't think anyone wants to read them routinely. I certainly don't. > If one is interested in a particular failure, it's easy enough to go > into the list and find the right one. > OK then. > Ian.