This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-API] [PATCH] imported patch removing-warnings

To: Jonathan Knowles <Jonathan.Knowles@xxxxxxxxxxxxx>
Subject: Re: [Xen-API] [PATCH] imported patch removing-warnings
From: Rok Strnisa <rok.strnisa@xxxxxxxxxx>
Date: Wed, 10 Nov 2010 12:38:39 +0000
Accept-language: en-US
Acceptlanguage: en-US
Cc: Vincent Hanquez <Vincent.Hanquez@xxxxxxxxxxxxx>, Dave Scott <Dave.Scott@xxxxxxxxxxxxx>, "xen-api@xxxxxxxxxxxxxxxxxxx" <xen-api@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Wed, 10 Nov 2010 04:39:49 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4CDA8E27.3030604@xxxxxxxxxxxxx>
List-help: <mailto:xen-api-request@lists.xensource.com?subject=help>
List-id: Discussion of API issues surrounding Xen <xen-api.lists.xensource.com>
List-post: <mailto:xen-api@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-api>, <mailto:xen-api-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-api>, <mailto:xen-api-request@lists.xensource.com?subject=unsubscribe>
References: <403764544b97988f2e3d.1289323667@rok-desktop> <4CDA61E7.5060509@xxxxxxxxxxxxx> <B462D1536FED1140871BC97AB218A6598EFA3A1CC7@xxxxxxxxxxxxxxxxxxxxxxxxx> <4CDA8827.1060607@xxxxxxxxxxxxx> <B462D1536FED1140871BC97AB218A6598EFA3A1CCA@xxxxxxxxxxxxxxxxxxxxxxxxx> <4CDA8E27.3030604@xxxxxxxxxxxxx>
Sender: xen-api-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcuA1FLWsGAQqkg7QbaKTnYUKlMFRw==
Thread-topic: [Xen-API] [PATCH] imported patch removing-warnings
I've already started writing a tool for that :)

On 10 Nov 2010, at 12:21, "Jonathan Knowles" <Jonathan.Knowles@xxxxxxxxxxxxx> 

> On 10/11/10 12:08, Rok Strnisa wrote:
>> Because this will take some effort, I've decided to not do it all
>> myself, but rather use the source control to identify who is
>> responsible for each warning, and delegate it to them --- originally
>> an idea by Jonathan Knowles.
> Yes -- it ought to be possible to distribute this work:
> 1. grep the results of a successful build for warnings
> 2. convert the warnings into a warning list w, where w = [(file, line)]
> 3. use hg annot to identify the person that last touched each line
> 4. partition list w into a per-user list of warnings: [(user, [(file, 
> line)])].
> 5. create a bug report for each user, along with their list of warnings.
> Thoughts?
> Jonathan

xen-api mailing list