qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] [RFC] QEMU Code Audit Team


From: Anthony Liguori
Subject: Re: [Qemu-devel] [RFC] QEMU Code Audit Team
Date: Tue, 10 Jan 2012 08:21:14 -0600
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.23) Gecko/20110922 Lightning/1.0b2 Thunderbird/3.1.15

On 01/10/2012 07:33 AM, Kevin Wolf wrote:
Am 10.01.2012 14:22, schrieb Anthony Liguori:
On 01/10/2012 06:58 AM, Kevin Wolf wrote:
Probably we need to attack the reviewing problem first: That I review
all block patches myself worked well as long as we were two or three
people in that area, but today it doesn't scale any more without
lowering the review standards - and I don't want to do that. Maybe we
should introduce something like "One Reviewed-by buys you two
Signed-off-bys for your own patches" ;-)

I think one thing that helps is to make sure for maintainers to include
Reviewed-bys in commits.  The script I use (below) takes a mbox with the full
thread and folks Reviewed-by/Tested-bys into the original patch spitting out an
mbox with just the patches and tags.

That way people are getting credit in git for doing reviews.  It's a small
incentive but every little bit helps.

http://git.codemonkey.ws/cgit/mbox-filter.git/

I usually do that, although manually.

Of the 487 patches I have committed, 71 have a Reviewed-by tag in the
commit message. Maybe I've missed to include it for some, but that's
about the ratio that feels realistic to me.

That's 14.6%. My rate over the past year is 15.8% so you're probably catching the vast majority of them.

The tree overall is 12.6% for the entire year so I guess that means the majority of Reviewed-by's are being added.

Regards,

Anthony Liguori


Kevin





reply via email to

[Prev in Thread] Current Thread [Next in Thread]