From: Patrick Palka <patrick@parcs.ath.cx>
To: Joel Brobecker <brobecker@adacore.com>
Cc: Pedro Alves <palves@redhat.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH] Fix the processing of Meta-key commands in TUI
Date: Sun, 23 Nov 2014 12:41:00 -0000 [thread overview]
Message-ID: <CA+C-WL8Kjk-7VdP=cSX-N8MOg9iKGUcRrryNeXniQJwRET_2cg@mail.gmail.com> (raw)
In-Reply-To: <20141123100817.GG5774@adacore.com>
On Sun, Nov 23, 2014 at 5:08 AM, Joel Brobecker <brobecker@adacore.com> wrote:
> Patrick,
>
>> Attached is the patch that Pedro approved, augmented with a comment
>> describing the potential problem with 3+ byte sequences. I wonder if
>> someone could commit this for me?
> [...]
>> gdb/ChangeLog:
>>
>> * event-top.h (call_stdin_event_handler_again_p): Declare.
>> * event-top.c (call_stdin_event_handler_again_p): Define.
>> (stdin_event_handler): Use it.
>> * tui/tui-io.c (tui_getc): Prepare to call the stdin event
>> handler again if there is pending input following a
>> start sequence.
>
> Your patch did not apply to today's sources. The conflict was trivially
> resolved, but it would be good if you could check the "master" branch
> out, and rebuild, to make sure your fix was correctly pushed.
Looks like the patch was correctly pushed. Thanks Joel.
>
> Attached is what I did push.
>
> Thanks for the patch.
> --
> Joel
prev parent reply other threads:[~2014-11-23 12:41 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-22 20:44 Patrick Palka
2014-08-27 17:06 ` Pedro Alves
2014-08-27 18:25 ` Patrick Palka
2014-08-28 11:22 ` Pedro Alves
2014-08-28 13:10 ` Patrick Palka
2014-08-28 14:13 ` Patrick Palka
2014-08-28 15:59 ` Pedro Alves
2014-08-28 16:22 ` Patrick Palka
2014-08-28 17:41 ` Patrick Palka
2014-08-28 17:44 ` Patrick Palka
2014-08-28 11:31 ` Pedro Alves
2014-08-28 14:18 ` Patrick Palka
2014-08-28 16:13 ` Pedro Alves
2014-08-28 16:26 ` Patrick Palka
2014-11-14 19:12 ` Patrick Palka
2014-11-23 10:08 ` Joel Brobecker
2014-11-23 12:41 ` Patrick Palka [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='CA+C-WL8Kjk-7VdP=cSX-N8MOg9iKGUcRrryNeXniQJwRET_2cg@mail.gmail.com' \
--to=patrick@parcs.ath.cx \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.com \
/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