From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: "Daniel P. Berrangé" <berrange@redhat.com>, qemu-devel@nongnu.org
Cc: "Volker Rümelin" <vr_qemu@t-online.de>
Subject: Re: [PATCH] ui: update keycodemapdb submodule commit
Date: Mon, 11 May 2020 14:32:53 +0200 [thread overview]
Message-ID: <e98883d2-7afc-442e-b01e-fb8278f80cb6@redhat.com> (raw)
In-Reply-To: <20200505125713.940953-1-berrange@redhat.com>
+Volker
On 5/5/20 2:57 PM, Daniel P. Berrangé wrote:
> Primarily this is to pull in a fix for Win32 keycodes. The other useful
> change is the removal of build timestamp from generated files which is
> desirable for reproducable builds.
>
> The make rules need updating due to slightly changed CLI syntax - more
> args must now come after the command name.
>
> 27acf0ef828bf719b2053ba398b195829413dbdd Fix win32 keycode for VK_OEM_102
> 317d3eeb963a515e15a63fa356d8ebcda7041a51 Add support for generating RST formatted docs pages
> 7381b9bfadd31c4c9e9a10b5bb5032f9189d4352 Introduce separate args for title & subtitle with docs generator
> 6280c94f306df6a20bbc100ba15a5a81af0366e6 keymap-gen: Name sections in pod output
> df4e56f8fab65ba714ec18f4e7338a966a1620ad Add an empty meson project
> 16e5b0787687d8904dad2c026107409eb9bfcb95 remove buildtime from generated files
> 044f21dd0d4f62519aae9f1d53a026407a0b664f add header file generators
> 7779876a6b06755e3bb2c94ee3ded50635bcb0fa c++: add extern declaration to the generated file
> 0e0a317889464397d6f1ae03aad0d2ca593aab04 move CLanguageGenerator closer to CLanguageGenerator itself
>
> Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
> ---
> Makefile | 4 ++--
> ui/keycodemapdb | 2 +-
> 2 files changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/Makefile b/Makefile
> index 34275f57c9..5f2b63b1cd 100644
> --- a/Makefile
> +++ b/Makefile
> @@ -310,10 +310,10 @@ ui/input-keymap-%.c: $(KEYCODEMAP_GEN) $(KEYCODEMAP_CSV) $(SRC_PATH)/ui/Makefile
> $(call quiet-command,\
> stem=$* && src=$${stem%-to-*} dst=$${stem#*-to-} && \
> test -e $(KEYCODEMAP_GEN) && \
> - $(PYTHON) $(KEYCODEMAP_GEN) \
> + $(PYTHON) $(KEYCODEMAP_GEN) code-map \
> --lang glib2 \
> --varname qemu_input_map_$${src}_to_$${dst} \
> - code-map $(KEYCODEMAP_CSV) $${src} $${dst} \
> + $(KEYCODEMAP_CSV) $${src} $${dst} \
> > $@ || rm -f $@, "GEN", "$@")
>
> $(KEYCODEMAP_GEN): .git-submodule-status
> diff --git a/ui/keycodemapdb b/ui/keycodemapdb
> index 6b3d716e2b..27acf0ef82 160000
> --- a/ui/keycodemapdb
> +++ b/ui/keycodemapdb
> @@ -1 +1 @@
> -Subproject commit 6b3d716e2b6472eb7189d3220552280ef3d832ce
> +Subproject commit 27acf0ef828bf719b2053ba398b195829413dbdd
>
Reviewed-by: Philippe Mathieu-Daudé <philmd@redhat.com>
Tested-by: Philippe Mathieu-Daudé <philmd@redhat.com>
next prev parent reply other threads:[~2020-05-11 12:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-05 12:57 [PATCH] ui: update keycodemapdb submodule commit Daniel P. Berrangé
2020-05-11 12:32 ` Philippe Mathieu-Daudé [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-01-27 18:08 Daniel P. Berrangé
2021-01-27 18:53 ` Philippe Mathieu-Daudé
2021-07-05 7:59 Akihiko Odaki
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=e98883d2-7afc-442e-b01e-fb8278f80cb6@redhat.com \
--to=philmd@redhat.com \
--cc=berrange@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=vr_qemu@t-online.de \
/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).