From: Paolo Bonzini <pbonzini@redhat.com>
To: Kevin Wolf <kwolf@redhat.com>
Cc: qemu-devel@nongnu.org, kraxel@redhat.com
Subject: Re: [Qemu-devel] [PATCH] gtk: implement set_echo
Date: Wed, 17 Feb 2016 15:05:06 +0100 [thread overview]
Message-ID: <56C47E12.4000007@redhat.com> (raw)
In-Reply-To: <20160217135340.GF29494@noname.str.redhat.com>
On 17/02/2016 14:53, Kevin Wolf wrote:
> Waiting didn't fix the bug, so I tried a git bisect now and it pointed
> me to this commit.
>
> I'm using HMP with the default vc backend. Starting with this commit,
> the echo is broken sometimes, in a way that the first character in the
> entered command is duplicated for each new character I enter, like this:
>
> (qemu) ii
> (qemu) iiin
> (qemu) iiiinf
> (qemu) iiiiinfo
>
> This doesn't happen always, but often enough to be annoying.
The patch for it is already on the way.
Paolo
next prev parent reply other threads:[~2016-02-17 14:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-17 12:47 [Qemu-devel] [PATCH] gtk: implement set_echo Paolo Bonzini
2016-01-08 13:11 ` Paolo Bonzini
2016-01-08 13:28 ` Gerd Hoffmann
2016-02-17 13:53 ` Kevin Wolf
2016-02-17 14:05 ` Paolo Bonzini [this message]
2016-02-21 20:36 ` Jan Kiszka
2016-02-22 8:33 ` 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=56C47E12.4000007@redhat.com \
--to=pbonzini@redhat.com \
--cc=kraxel@redhat.com \
--cc=kwolf@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 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).