From: Markus Armbruster <armbru@redhat.com>
To: Marcelo Tosatti <mtosatti@redhat.com>
Cc: Gerd Hoffmann <kraxel@redhat.com>, qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] x-input-send-event marked as experimental
Date: Fri, 18 Dec 2015 21:01:33 +0100 [thread overview]
Message-ID: <874mffy19e.fsf@blackfin.pond.sub.org> (raw)
In-Reply-To: <20151218192042.GA27278@amt.cnet> (Marcelo Tosatti's message of "Fri, 18 Dec 2015 17:20:43 -0200")
Marcelo Tosatti <mtosatti@redhat.com> writes:
> Gerd,
>
> commit df5b2adb7398d71016ee469f71e52075ed95e04e
> Author: Gerd Hoffmann <kraxel@redhat.com>
> Date: Tue Nov 25 14:54:17 2014 +0100
>
> input: move input-send-event into experimental namespace
>
> Ongoing discussions on how we are going to specify the console,
> so tag the command as experiental so we can refine things in
> the 2.3 development cycle.
>
> So what is the problem here again?
> input-send-event can send an input event to a
> particular console, so that (the console number)
> has to be specified somehow.
>
> But, its already there, you can specify the console:
>
> -{ 'command': 'input-send-event',
> +{ 'command': 'x-input-send-event',
> 'data': { '*console':'int', 'events': [ 'InputEvent' ] } }
>
> So what its waiting for to be moved out of experimental status?
See
* http://lists.gnu.org/archive/html/qemu-devel/2014-11/msg03425.html
Message-ID: <87zjbgvbp0.fsf@blackfin.pond.sub.org>
and the thread around it
* http://lists.gnu.org/archive/html/qemu-devel/2015-11/msg02935.html
Message-ID: <1447319343.1400.39.camel@redhat.com>
* commit 513e7cd input: Document why x-input-send-event is still
experimental
next prev parent reply other threads:[~2015-12-18 20:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-18 19:20 [Qemu-devel] x-input-send-event marked as experimental Marcelo Tosatti
2015-12-18 20:01 ` Markus Armbruster [this message]
2015-12-21 11:53 ` Marcelo Tosatti
2016-01-12 9:54 ` Markus Armbruster
2016-01-12 10:39 ` Gerd Hoffmann
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=874mffy19e.fsf@blackfin.pond.sub.org \
--to=armbru@redhat.com \
--cc=kraxel@redhat.com \
--cc=mtosatti@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.