From: Programmingkid <programmingkidx@gmail.com>
To: Eric Blake <eblake@redhat.com>
Cc: "Daniel P. Berrange" <berrange@redhat.com>,
"qemu-devel@nongnu.org qemu-devel" <qemu-devel@nongnu.org>,
Gerd Hoffmann <kraxel@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v3 00/12] Convert over to use keycodemapdb
Date: Mon, 14 Aug 2017 14:49:07 -0400 [thread overview]
Message-ID: <05CBF3D0-1FBE-4139-B968-9ED138206FFC@gmail.com> (raw)
In-Reply-To: <b4268987-e25d-02fc-3931-7b9576969cc5@redhat.com>
> On Aug 14, 2017, at 2:20 PM, Eric Blake <eblake@redhat.com> wrote:
>
> On 08/14/2017 12:20 PM, Programmingkid wrote:
>>> These are based against git master, just save the series and then 'git am'
>>> the lot in one go.
>>
>> Is there a tool that can be used to download a series of patches from a mailing list? Copying and pasting patches sometimes introduces problems.
>
> 'git am'. I find it works well to save the patch series into a single
> mailbox, then save that mailbox for the file to feed to git am.
>
Thank you for the information. Can this be down when receiving emails as a digest, or does it only work for individual emails?
next prev parent reply other threads:[~2017-08-14 18:49 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1778.1502715001.21954.qemu-devel@nongnu.org>
2017-08-14 13:39 ` [Qemu-devel] [PATCH v3 00/12] Convert over to use keycodemapdb Programmingkid
2017-08-14 14:00 ` Daniel P. Berrange
2017-08-14 17:20 ` Programmingkid
2017-08-14 18:20 ` Eric Blake
2017-08-14 18:49 ` Programmingkid [this message]
2017-08-14 19:07 ` Eric Blake
2017-08-14 20:30 ` Philippe Mathieu-Daudé
2017-08-14 18:46 Programmingkid
2017-08-15 8:38 ` Daniel P. Berrange
2017-08-15 13:49 ` Programmingkid
2017-08-15 13:49 ` Daniel P. Berrange
2017-08-15 14:44 ` Programmingkid
-- strict thread matches above, loose matches on Subject: below --
2017-08-14 12:49 Daniel P. Berrange
2017-08-14 13:05 ` no-reply
2017-08-14 13:06 ` no-reply
2017-08-14 13:06 ` no-reply
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=05CBF3D0-1FBE-4139-B968-9ED138206FFC@gmail.com \
--to=programmingkidx@gmail.com \
--cc=berrange@redhat.com \
--cc=eblake@redhat.com \
--cc=kraxel@redhat.com \
--cc=qemu-devel@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 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).