From: Thomas Huth <thuth@redhat.com>
To: Kashyap Chamarthy <kchamart@redhat.com>
Cc: "Peter Maydell" <peter.maydell@linaro.org>,
"Daniel P. Berrangé" <berrange@redhat.com>,
"Eric Blake" <eblake@redhat.com>,
"Michael Tokarev" <mjt@tls.msk.ru>,
qemu-devel@nongnu.org, "Laurent Vivier" <laurent@vivier.eu>,
"John Snow" <jsnow@redhat.com>,
"Stefan Hajnoczi" <stefanha@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>
Subject: Re: [PATCH v3 3/3] docs: rSTify the "SubmitAPatch" wiki
Date: Wed, 17 Nov 2021 15:43:56 +0100 [thread overview]
Message-ID: <cd1b4dcd-01c3-33e0-6525-cbcbcc24a165@redhat.com> (raw)
In-Reply-To: <YZTYo3H6TZheGbrj@paraplu>
On 17/11/2021 11.25, Kashyap Chamarthy wrote:
...
>>> +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 ".".
>>
>> That ".". looks a little bit weird in the output ... maybe we should replace
>> it with "does not end with a dot." ?
>
> Re-looking the output, yes it does look odd. And yes, your amendment
> is good.
I haven't updated that one while picking up the patch - so we might want to
fix it with an additional patch on top.
>>> +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
>>
>> That --- gets translated into a — character ... I'll replace the "---" with
>> ``---`` to fix it.
>
> Ah, when I locally ran `rst2html5 submitting-a-patch.rst
> submitting-a-patch.html` it retained the "---", but when I built QEMU
> (`configure --target-list=x86_64-softmmu --enable-docs`), Sphinx does
> turn it into an em-dash (—), and missed to notice it.
>
> Thanks for the careful review and submitting the PR. I'm assuming I
> don't need to respin a v4.
Right, patches have been merged now.
Something I just noticed afterwards, after looking at the pages online:
https://www.qemu.org/docs/master/devel/submitting-a-pull-request.html uses
"Submit" in the heading, while
https://www.qemu.org/docs/master/devel/submitting-a-patch.html uses
"Submitting" ... looks a little bit inconsequent ... should we change it to
use one form only? The Wiki used "submit", not "submitting", so maybe use
that one?
Thomas
next prev parent reply other threads:[~2021-11-17 14:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-10 14:48 [PATCH v3 0/3] rSTify contribution-related wiki pages Kashyap Chamarthy
2021-11-10 14:49 ` [PATCH v3 1/3] docs: rSTify the "TrivialPatches" wiki Kashyap Chamarthy
2021-11-10 14:49 ` [PATCH v3 2/3] docs: rSTify the "SubmitAPullRequest" wiki Kashyap Chamarthy
2021-11-10 14:49 ` [PATCH v3 3/3] docs: rSTify the "SubmitAPatch" wiki Kashyap Chamarthy
2021-11-17 9:08 ` Thomas Huth
2021-11-17 10:25 ` Kashyap Chamarthy
2021-11-17 14:43 ` Thomas Huth [this message]
2021-11-17 15:35 ` Kashyap Chamarthy
2021-11-10 15:34 ` [PATCH v3 0/3] rSTify contribution-related wiki pages Philippe Mathieu-Daudé
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=cd1b4dcd-01c3-33e0-6525-cbcbcc24a165@redhat.com \
--to=thuth@redhat.com \
--cc=berrange@redhat.com \
--cc=eblake@redhat.com \
--cc=jsnow@redhat.com \
--cc=kchamart@redhat.com \
--cc=laurent@vivier.eu \
--cc=mjt@tls.msk.ru \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.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).