From: Markus Armbruster <armbru@redhat.com>
To: Programmingkid <programmingkidx@gmail.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
Gerd Hoffmann <kraxel@redhat.com>,
qemu-devel qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] ping [PATCH 0/3] Switch USB HID to QKeyCode
Date: Mon, 11 Apr 2016 08:52:17 +0200 [thread overview]
Message-ID: <87inzoprha.fsf@dusky.pond.sub.org> (raw)
In-Reply-To: <466C6348-C01A-48AA-996B-4231047DC7C7@gmail.com> (Programmingkid's message of "Sun, 10 Apr 2016 22:58:06 -0400")
You can improve your chances for people looking at your patches: don't
require them to go hunting for the parts! Use proper threading.
If you can't get git-send-email to work with gmail (unlike other gmail
users), get yourself an email address you can get to work.
prev parent reply other threads:[~2016-04-11 6:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-25 16:06 [Qemu-devel] [PATCH 0/3] Switch USB HID to QKeyCode Programmingkid
2016-04-11 2:58 ` [Qemu-devel] ping " Programmingkid
2016-04-11 6:52 ` Markus Armbruster [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-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=87inzoprha.fsf@dusky.pond.sub.org \
--to=armbru@redhat.com \
--cc=kraxel@redhat.com \
--cc=peter.maydell@linaro.org \
--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).