From: Simon Marchi <simon.marchi@polymtl.ca>
To: Tom Tromey <tom@tromey.com>
Cc: Philipp Rudo <prudo@linux.vnet.ibm.com>,
gdb-patches@sourceware.org, arnez@linux.vnet.ibm.com,
Patrick Monnerat <Patrick.Monnerat@datasphere.ch>
Subject: Re: [PATCH 00/11] Cleanup deprecated_*_hooks in defs.h
Date: Tue, 28 Feb 2017 15:52:00 -0000 [thread overview]
Message-ID: <51267a8c31e5193bdc3a3e9d7c38be48@polymtl.ca> (raw)
In-Reply-To: <87innuwd0x.fsf@tromey.com>
On 2017-02-28 10:28, Tom Tromey wrote:
> I don't know whether Insight is still supported or if being able to
> build it is still worthwhile to gdb; but in the past this is why these
> hooks weren't removed.
[CCing Patrick, maintainer of Insight]
AFAIK, we are doing a best effort of keeping Insight happy. I've
adapted some of my patches and Insight in the past to keep Insight
building, and it was not an effort of significant size (things like
changing a function signature).
However, I think we are in a weird position where we have some
deprecated features used by a program that we don't want to break, but
that will most likely not change to stop using these features. If we
want to exit that endless loop some day, I guess Insight should be
converted to use MI, like other frontends.
next prev parent reply other threads:[~2017-02-28 15:52 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-28 14:50 Philipp Rudo
2017-02-28 14:50 ` [PATCH 11/11] Remove deprecated_print_frame_info_listing_hook Philipp Rudo
2017-02-28 14:50 ` [PATCH 08/11] Remove unused deprecated_{attach|detach}_hook Philipp Rudo
2017-02-28 14:50 ` [PATCH 06/11] Remove unused deprecated_context_hook Philipp Rudo
2017-02-28 14:50 ` [PATCH 10/11] Remove unused deprecated_ui_load_progress_hook Philipp Rudo
2017-02-28 14:50 ` [PATCH 03/11] Remove unused deprecated_warning_hook Philipp Rudo
2017-02-28 14:50 ` [PATCH 02/11] Remove unused deprecated_ui_loop_hook Philipp Rudo
2017-02-28 14:50 ` [PATCH 09/11] Remove unused deprecated_call_command_hook Philipp Rudo
2017-02-28 14:50 ` [PATCH 01/11] Remove unused deprecated_{pre|post}_add_symbol_hook Philipp Rudo
2017-02-28 14:50 ` [PATCH 05/11] Remove unused deprecated_readline{_begin|_end}_hook Philipp Rudo
2017-02-28 15:28 ` [PATCH 00/11] Cleanup deprecated_*_hooks in defs.h Tom Tromey
2017-02-28 15:52 ` Simon Marchi [this message]
2017-03-01 9:11 ` Philipp Rudo
2017-03-01 22:17 ` Yao Qi
2017-02-28 18:01 ` [PATCH 04/11] Remove unused deprecated_interactive_hook Philipp Rudo
2017-02-28 19:37 ` [PATCH 00/11] Cleanup deprecated_*_hooks in defs.h Keith Seitz
2017-02-28 19:45 ` [PATCH 07/11] Remove unused deprecated_target_wait_hook Philipp Rudo
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=51267a8c31e5193bdc3a3e9d7c38be48@polymtl.ca \
--to=simon.marchi@polymtl.ca \
--cc=Patrick.Monnerat@datasphere.ch \
--cc=arnez@linux.vnet.ibm.com \
--cc=gdb-patches@sourceware.org \
--cc=prudo@linux.vnet.ibm.com \
--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