From: Eric Blake <eblake@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: "Chen Gang" <gang.chen.5i5j@gmail.com>,
"QEMU Trivial" <qemu-trivial@nongnu.org>,
"Michael Tokarev" <mjt@tls.msk.ru>,
"Markus Armbruster" <armbru@redhat.com>,
"QEMU Developers" <qemu-devel@nongnu.org>,
"Anthony Liguori" <aliguori@amazon.com>,
"Andreas Färber" <afaerber@suse.de>
Subject: [Qemu-trivial] commit log tips [was: [Qemu-devel] [PATCH trivial] vl: Avoid to close stdout after finish 'writeconfig' option]
Date: Tue, 22 Apr 2014 13:45:50 -0600 [thread overview]
Message-ID: <5356C6EE.5040005@redhat.com> (raw)
In-Reply-To: <CAFEAcA9E6E7qt9X1QfQm3Gaa4PGt21MNdSB6ok94ht3zQK459A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1834 bytes --]
On 04/22/2014 01:18 PM, Peter Maydell wrote:
> On 22 April 2014 17:31, Eric Blake <eblake@redhat.com> wrote:
>> Hmm, maybe we should update the qemu wiki?
>> http://wiki.qemu.org/Contribute/SubmitAPatch doesn't mention the qemu
>> preferred style (you pointed to the GNOME style, but at least GNU
>> coreutils explicitly prefers lowercase).
>>
>> At any rate, I'm not going to reject a patch based on capitalization,
>
> Yeah, it doesn't really seem worth trying to enforce niceties
> of style here -- the effort required doesn't seem to really match
> the benefit, and we already have a lot of hoops we make new
> submitters jump through. "[file or area being patched]: [reasonably
> descriptive short summary]" is about the limit I personally feel
> comfortable insisting on.
So, given this discussion, I enhanced the existing paragraph in the wiki
page mentioned above to include a couple more sentences:
'''Write a good commit message'''. QEMU follows the usual standard for
git commit messages: the first line (which becomes the email subject
line) is "subsystem: single line summary of change". Whether the "single
line summary of change" starts with a capital is a matter of taste, but
we prefer that the summary does not end in ".". Look at <code>git
short-log 30</code> for an idea of sample subject lines. Then there is
a blank line and a more detailed description of the patch, another blank
and your Signed-off-by: line. The body of the commit message is a good
place to document why your change is important. Don't include comments
like "This is a suggestion for fixing this bug" (they can go below the
"---" line in the email so they don't go into the final commit message).
--
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: 604 bytes --]
prev parent reply other threads:[~2014-04-22 19:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-20 12:05 [Qemu-trivial] [PATCH trivial] vl: Avoid to close stdout after finish 'writeconfig' option Chen Gang
2014-04-21 15:09 ` [Qemu-trivial] [Qemu-devel] " Eric Blake
2014-04-22 1:00 ` Chen Gang
2014-04-22 16:06 ` Andreas Färber
2014-04-22 16:31 ` Eric Blake
2014-04-22 19:18 ` Peter Maydell
2014-04-22 19:45 ` 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=5356C6EE.5040005@redhat.com \
--to=eblake@redhat.com \
--cc=afaerber@suse.de \
--cc=aliguori@amazon.com \
--cc=armbru@redhat.com \
--cc=gang.chen.5i5j@gmail.com \
--cc=mjt@tls.msk.ru \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.