From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: devel@edk2.groups.io, rebecca@bsdio.com,
Jordan Justen <jordan.l.justen@intel.com>,
Laszlo Ersek <lersek@redhat.com>,
Ard Biesheuvel <ard.biesheuvel@linaro.org>
Subject: Re: [edk2-devel] [PATCH v2 1/3] OvmfPkg/build.sh: use POSIX 'command -v' instead of 'which'.
Date: Thu, 25 Jul 2019 15:36:00 +0200 [thread overview]
Message-ID: <7dc6c2e3-91f3-fa8f-c827-a08f0fcae13a@redhat.com> (raw)
In-Reply-To: <ce3a1963-c94f-ecd0-e44c-55d7d082a61f@bsdio.com>
On 7/25/19 2:45 PM, rebecca@bsdio.com wrote:
> On 2019-07-25 05:07, Philippe Mathieu-Daudé wrote:
>> It would be quicker to reply to your series if you use a cover letter.
>> (I'd have replied "series: Reviewed-by" instead of going thru each patch).
>
> Thanks, I'll try and remember that in future. I'm still learning how
> best to send patches using "git send-email".
Then I recommend you to look at the git-publish tool :)
I haven't used 'git send-email' since I started to use it:
https://github.com/stefanha/git-publish
prev parent reply other threads:[~2019-07-25 13:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-24 21:44 [PATCH v2 1/3] OvmfPkg/build.sh: use POSIX 'command -v' instead of 'which' rebecca
2019-07-24 21:44 ` [PATCH v2 2/3] OvmfPkg/build.sh: use newer '-drive if=pflash' syntax when running qemu rebecca
2019-07-25 2:56 ` Jordan Justen
2019-07-25 11:07 ` [edk2-devel] " Philippe Mathieu-Daudé
2019-07-24 21:44 ` [PATCH v2 3/3] OvmfPkg/build.sh: remove $ADD_QEMU_HDA rebecca
2019-07-24 22:56 ` Jordan Justen
2019-07-30 2:24 ` [edk2-devel] " rebecca
2019-07-30 5:53 ` Jordan Justen
2019-07-25 11:08 ` Philippe Mathieu-Daudé
2019-07-25 11:07 ` [edk2-devel] [PATCH v2 1/3] OvmfPkg/build.sh: use POSIX 'command -v' instead of 'which' Philippe Mathieu-Daudé
2019-07-25 12:45 ` rebecca
2019-07-25 13:36 ` Philippe Mathieu-Daudé [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-list 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=7dc6c2e3-91f3-fa8f-c827-a08f0fcae13a@redhat.com \
--to=devel@edk2.groups.io \
/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