From: Hannes Domani via Gdb-patches <gdb-patches@sourceware.org>
To: Joel Brobecker <brobecker@adacore.com>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
Pedro Alves <pedro@palves.net>
Cc: "bernd.edlinger@hotmail.de" <bernd.edlinger@hotmail.de>,
"tom@tromey.com" <tom@tromey.com>,
"sergey.belyashov@gmail.com" <sergey.belyashov@gmail.com>
Subject: Re: GDB 11 branching update (2021-06-13)
Date: Thu, 17 Jun 2021 15:01:49 +0000 (UTC) [thread overview]
Message-ID: <261071571.1770975.1623942109068@mail.yahoo.com> (raw)
In-Reply-To: <404636b8-f579-f5ec-09ae-88fd8ca9a299@palves.net>
Am Donnerstag, 17. Juni 2021, 13:16:42 MESZ hat Pedro Alves <pedro@palves.net> Folgendes geschrieben:
> On 2021-06-13 3:31 p.m., Joel Brobecker wrote:
>
> > * [Bernd/PedroA/TomT] TUI issues from mouse-support patch
> > https://sourceware.org/pipermail/gdb-patches/2021-June/179541.html
>
> (FWIW, this was HannesD, not Bernd)
>
>
> >
> > Under discussion, but looks like there is good progress.
> > It's a bit difficult for me to follow the discussions because
> > I don't know TUI -- would you let me know when you think
> > all blocking issues have been resolved?
>
>
> I've merged the fix for this now. I believe the issue is resolved.
>
> I'd still like to get the NEWS and docs bits for the TUI mouse in, though.
>
> I'll take a look at those.
I would like it if the locals window also made it in:
https://sourceware.org/pipermail/gdb-patches/2021-June/179539.html
Since this is the main reason I started to implement mouse support at all.
Hannes
next prev parent reply other threads:[~2021-06-17 15:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-13 14:31 Joel Brobecker
2021-06-13 14:57 ` Philippe Waroquiers via Gdb-patches
2021-06-13 15:30 ` Joel Brobecker
2021-06-14 7:44 ` Kevin Buettner via Gdb-patches
2021-06-17 7:36 ` Rainer Orth
2021-06-17 11:16 ` Pedro Alves
2021-06-17 15:01 ` Hannes Domani via Gdb-patches [this message]
2021-07-02 15:34 ` Pedro Alves
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=261071571.1770975.1623942109068@mail.yahoo.com \
--to=gdb-patches@sourceware.org \
--cc=bernd.edlinger@hotmail.de \
--cc=brobecker@adacore.com \
--cc=pedro@palves.net \
--cc=sergey.belyashov@gmail.com \
--cc=ssbssa@yahoo.de \
--cc=tom@tromey.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