qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: Christoph Hellwig <hch@infradead.org>
Cc: Chris Wright <chrisw@redhat.com>,
	qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: [Qemu-devel] Re: KVM call minutes for June 15
Date: Tue, 15 Jun 2010 11:13:20 -0500	[thread overview]
Message-ID: <4C17A6A0.2010203@codemonkey.ws> (raw)
In-Reply-To: <20100615154153.GA2707@infradead.org>

On 06/15/2010 10:41 AM, Christoph Hellwig wrote:
> On Tue, Jun 15, 2010 at 08:18:12AM -0700, Chris Wright wrote:
>    
>> KVM/qemu patches
>> - patch rate is high, documentation is low, review is low
>> - patches need to include better descriptions and documentation
>>    - will slow down patch writers
>>    - will make it easier for patch reviewers
>>      
> What is the qemu patch review policy anyway?

We don't really have a coherent policy.  Suggestions for improvement are 
always appreciated.

>    There are no
> "Reviewed-by:" included in the actual commits,

Reviewed-by/Ack-by's are pretty helpful for me.  In terms of including 
them in commit messages, if there's a strong feeling that that would be 
helpful then it's something I can look at doing but it also requires a 
fair bit of manual work during commit.

>   and the requirement
> for a positive review also seem to vary a lot, up to the point that
> some commiters commit code that has never hit a public mailing list
> before.
>    

That really shouldn't happen and if it does, please point it out on the 
list.

Regards,

Anthony Liguori

> --
> To unsubscribe from this list: send the line "unsubscribe kvm" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>    

  reply	other threads:[~2010-06-15 16:15 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-15 15:18 [Qemu-devel] KVM call minutes for June 15 Chris Wright
2010-06-15 15:41 ` [Qemu-devel] " Christoph Hellwig
2010-06-15 16:13   ` Anthony Liguori [this message]
2010-06-16  6:55     ` Markus Armbruster
2010-06-16  8:58       ` Yoshiaki Tamura
2010-06-16 11:55       ` Arnd Bergmann
2010-06-16 18:07     ` Blue Swirl
2010-06-17  5:15   ` Aurelien Jarno
2010-06-16  8:58 ` Paolo Bonzini

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4C17A6A0.2010203@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --cc=chrisw@redhat.com \
    --cc=hch@infradead.org \
    --cc=kvm@vger.kernel.org \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).