[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] [OSSTEST PATCH 4/4] README.bisection: New consumer-oriented document
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. Ian. _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxx http://lists.xen.org/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |