qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Eric Blake <eblake@redhat.com>
To: Programmingkid <programmingkidx@gmail.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:07:55 -0500	[thread overview]
Message-ID: <36a10c9c-a074-7785-e09f-3372455fff34@redhat.com> (raw)
In-Reply-To: <05CBF3D0-1FBE-4139-B968-9ED138206FFC@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1833 bytes --]

On 08/14/2017 01:49 PM, Programmingkid wrote:
> 
>> 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.
>>>

> 
> Thank you for the information. Can this be down when receiving emails as a digest,

Presumably yes, and probably more likely if you selected MIME digests
(rather than plain text) on the list subscription page:
https://lists.gnu.org/mailman/options/qemu-devel

However, I personally don't use digest mail, so I can't really say what
git would do in that situation. You may get better answers by asking on
freenode's #git IRC channel (as there are more git experts there that
can quickly tell you what git can do).

If nothing else, you can always use:
https://lists.gnu.org/archive/html/qemu-devel/
to get at mbox formatted files for all patches within the entire month,
and use 'git am -i' to pick and choose which ones you want (may be
tedious if you can't figure out how to prune it, first).

(In situations like this, if you can't figure out how to make your
mailer properly save mbox-formatted mails for easy feeding to git, you
may want to reconsider whether you are using the best mailer on your end
- I know many developers on this list use mutt or thunderbird, but when
you start to get to other mail programs, you'll get better answers on a
git forum than you will here.  It doesn't help that your current choice
of mailer has a propensity to botch mail threading, by posting your
replies as top-level threads rather than in-reply-to the message you are
following up on)

-- 
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: 619 bytes --]

  reply	other threads:[~2017-08-14 19:08 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
2017-08-14 19:07           ` Eric Blake [this message]
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=36a10c9c-a074-7785-e09f-3372455fff34@redhat.com \
    --to=eblake@redhat.com \
    --cc=berrange@redhat.com \
    --cc=kraxel@redhat.com \
    --cc=programmingkidx@gmail.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).