From: Eric Blake <eblake@redhat.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: kwolf@redhat.com, aliguori@us.ibm.com, armbru@redhat.com,
qemu-devel@nongnu.org, pbonzini@redhat.com,
lcapitulino@redhat.com, Wenchao Xia <xiawenc@linux.vnet.ibm.com>
Subject: Re: [Qemu-devel] [PATCH V7 00/14] add qmp/hmp interfaces for internal snapshot info
Date: Mon, 04 Mar 2013 17:43:46 -0700 [thread overview]
Message-ID: <51353FC2.9030102@redhat.com> (raw)
In-Reply-To: <20130304131010.GC18476@stefanha-thinkpad.redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1225 bytes --]
On 03/04/2013 06:10 AM, Stefan Hajnoczi wrote:
>>> It is also useful to include QMP examples or the QMP docs in the cover
>>> letter so reviewers know what you are trying to achieve.
>>>
>> OK, a better explaination would be added in the cover-letter.
>
> Thanks. When reviewers don't know your goal at the start of their
> review, they may object to things that make sense at the end of the
> series because they do not have enough context yet. A series where the
> goal is unclear also risks a higher number of review-fix cycles because
> the reviewers haven't bought into the idea yet.
>
> It is in everyone's interest to explain the goal in the cover letter.
> Then the patches get reviewed more smoothly and merged faster.
This is good advice - so good that I added it to the wiki:
http://wiki.qemu.org/Contribute/SubmitAPatch
>
> This is a general thought I wanted to share and I struggle with it
> myself sometimes when I submit patch series.
Me too - but the nice thing about open source is that we can all learn
best practices from one another and become better at it :)
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 621 bytes --]
prev parent reply other threads:[~2013-03-05 0:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1361875228-15769-1-git-send-email-xiawenc@linux.vnet.ibm.com>
[not found] ` <1361875228-15769-9-git-send-email-xiawenc@linux.vnet.ibm.com>
[not found] ` <878v69hhl5.fsf@blackfin.pond.sub.org>
[not found] ` <512EBD01.8010906@linux.vnet.ibm.com>
2013-03-04 2:30 ` [Qemu-devel] [PATCH V7 08/14] qmp: add interface query-images Wenchao Xia
[not found] ` <1361875228-15769-10-git-send-email-xiawenc@linux.vnet.ibm.com>
[not found] ` <874ngxhhfv.fsf@blackfin.pond.sub.org>
[not found] ` <20130227162229.GJ2514@dhcp-200-207.str.redhat.com>
[not found] ` <513009B9.4090406@linux.vnet.ibm.com>
2013-03-04 3:20 ` [Qemu-devel] [PATCH V7 09/14] block: move bdrv_snapshot_find() to block.c Wenchao Xia
2013-03-04 13:02 ` Stefan Hajnoczi
2013-03-05 7:11 ` Wenchao Xia
2013-03-05 9:21 ` Stefan Hajnoczi
2013-03-05 10:08 ` Kevin Wolf
2013-03-05 10:52 ` Paolo Bonzini
[not found] ` <20130228155702.GJ18389@stefanha-thinkpad.redhat.com>
[not found] ` <513008B1.8080605@linux.vnet.ibm.com>
2013-03-04 13:10 ` [Qemu-devel] [PATCH V7 00/14] add qmp/hmp interfaces for internal snapshot info Stefan Hajnoczi
2013-03-05 0:43 ` Eric Blake [this message]
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=51353FC2.9030102@redhat.com \
--to=eblake@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=armbru@redhat.com \
--cc=kwolf@redhat.com \
--cc=lcapitulino@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.com \
--cc=xiawenc@linux.vnet.ibm.com \
/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).