From: "Daniel P. Berrange" <berrange@redhat.com>
To: Programmingkid <programmingkidx@gmail.com>
Cc: "qemu-devel@nongnu.org qemu-devel" <qemu-devel@nongnu.org>,
Gerd Hoffmann <kraxel@redhat.com>, Eric Blake <eblake@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v3 00/12] Convert over to use keycodemapdb
Date: Mon, 14 Aug 2017 15:00:03 +0100 [thread overview]
Message-ID: <20170814140003.GF8506@redhat.com> (raw)
In-Reply-To: <223B4DEC-A801-40E3-A118-33EBB9ED384D@gmail.com>
On Mon, Aug 14, 2017 at 09:39:56AM -0400, Programmingkid wrote:
>
> > On Aug 14, 2017, at 8:50 AM, qemu-devel-request@nongnu.org wrote:
> >
> > An update of:
> >
> > v1: https://lists.gnu.org/archive/html/qemu-devel/2017-08/msg02047.html
> > v2: https://lists.gnu.org/archive/html/qemu-devel/2017-08/msg02471.html
> >
> > The keycodemap project[1] provides a database mapping between
> > many different keysym/keycode/scancode sets, along with a
> > tool to generate mapping/lookup tables in various programming
> > languages. It is already used by GTK-VNC, SPICE-GTK and
> > libvirt.
> >
> > This series enables its use in QEMU, thus fixing a great
> > many bugs/ommissions in the 15+ key mapping tables people
> > have manually written for QEMU.
>
> Would you have a git repository that has all your patches already applied? It would make testing your patches a lot easier.
I only maintain stable public repos for pull requests.
These are based against git master, just save the series and then 'git am'
the lot in one go.
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2017-08-14 14:00 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 [this message]
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
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=20170814140003.GF8506@redhat.com \
--to=berrange@redhat.com \
--cc=eblake@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).