From: Laszlo Ersek <lersek@redhat.com>
To: Eric Blake <eblake@redhat.com>,
Dongjiu Geng <gengdongjiu@huawei.com>,
mst@redhat.com, imammedo@redhat.com, famz@redhat.com,
qemu-devel@nongnu.org, zhaoshenglong@huawei.com,
peter.maydell@linaro.org, qemu-arm@nongnu.org,
zhengqiang10@huawei.com, huangshaoyu@huawei.com,
wuquanming@huawei.com, zhihui.gao@huawei.com
Subject: Re: [Qemu-devel] [PATCH v4 1/3] ACPI: Add new ACPI structures and macros
Date: Mon, 10 Jul 2017 16:04:16 +0200 [thread overview]
Message-ID: <d48ec6cf-03b6-bf2b-1bed-1e2c34aaf5f0@redhat.com> (raw)
In-Reply-To: <df74267a-3f6f-b6f5-432f-40f8c04ab1f1@redhat.com>
On 07/10/17 15:54, Eric Blake wrote:
> On 07/10/2017 04:25 AM, Dongjiu Geng wrote:
>> (1) Add related APEI/HEST table structures and macros, these
>> definition refer to ACPI 6.1 and UEFI 2.6 spec.
>
> Your mail is missing In-Reply-To: and References: headers, which makes
> it appear as a new top-level thread for each patch. You'll want to
> figure out why you didn't properly link back to your 0/3 cover letter
> with Message-ID: <1499678736-5244-1-git-send-email-gengdongjiu@huawei.com>
>
Yes, the git-send-email options to use are:
--thread --no-chain-reply-to
Best to set them permanently in one's qemu clone,
$ git config --bool sendemail.thread true
$ git config --bool sendemail.chainreplyto false
This is called "shallow threading" (see git-send-email(1)).
Thanks
Laszlo
next prev parent reply other threads:[~2017-07-10 14:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-10 9:25 [Qemu-devel] [PATCH v4 1/3] ACPI: Add new ACPI structures and macros Dongjiu Geng
2017-07-10 13:54 ` Eric Blake
2017-07-10 14:04 ` Laszlo Ersek [this message]
2017-07-11 1:54 ` gengdongjiu
2017-07-11 2:01 ` gengdongjiu
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=d48ec6cf-03b6-bf2b-1bed-1e2c34aaf5f0@redhat.com \
--to=lersek@redhat.com \
--cc=eblake@redhat.com \
--cc=famz@redhat.com \
--cc=gengdongjiu@huawei.com \
--cc=huangshaoyu@huawei.com \
--cc=imammedo@redhat.com \
--cc=mst@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=wuquanming@huawei.com \
--cc=zhaoshenglong@huawei.com \
--cc=zhengqiang10@huawei.com \
--cc=zhihui.gao@huawei.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).