From: Eric Blake <eblake@redhat.com>
To: Laszlo Ersek <lersek@redhat.com>, Dongjiu Geng <gengdongjiu@huawei.com>
Cc: 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 resend v4 0/3] Generate APEI GHES table and dynamically record CPER
Date: Tue, 11 Jul 2017 08:58:28 -0500 [thread overview]
Message-ID: <d18b0a8d-5c34-ae4a-a60c-c451c8df9872@redhat.com> (raw)
In-Reply-To: <366f019e-50e8-03f4-9b8f-946ef318ca79@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 692 bytes --]
On 07/11/2017 08:43 AM, Laszlo Ersek wrote:
> So send the patches with
>
> git send-email *.patch
>
> or put all the patches into a temporary directory, and run
>
> git send-email patch-dir/
Or you can even skip patch files, and directly send things with one lass
chance in your editor:
git send-email -v5 -3 --annotate --cover-letter
[send the top three commits in my current git branch as a version 5
patch series, where I get to write the cover letter and tweak any of the
patches in my preferred $EDITOR before sending anything]
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3266
Virtualization: qemu.org | libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 604 bytes --]
next prev parent reply other threads:[~2017-07-11 13:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-11 6:46 [Qemu-devel] [PATCH resend v4 0/3] Generate APEI GHES table and dynamically record CPER Dongjiu Geng
2017-07-11 13:43 ` Laszlo Ersek
2017-07-11 13:58 ` Eric Blake [this message]
2017-07-12 1:52 ` gengdongjiu
-- strict thread matches above, loose matches on Subject: below --
2017-07-11 14:50 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=d18b0a8d-5c34-ae4a-a60c-c451c8df9872@redhat.com \
--to=eblake@redhat.com \
--cc=famz@redhat.com \
--cc=gengdongjiu@huawei.com \
--cc=huangshaoyu@huawei.com \
--cc=imammedo@redhat.com \
--cc=lersek@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).