From: Simon Marchi <simark@simark.ca>
To: Ulrich Weigand <uweigand@de.ibm.com>, Tom Tromey <tom@tromey.com>,
eliz@gnu.org
Cc: gdb-patches@sourceware.org
Subject: Re: [RFC/RFA] Remove Cell Broadband Engine debugging support
Date: Fri, 20 Sep 2019 01:47:00 -0000 [thread overview]
Message-ID: <1f8e7325-4ad5-7709-40e4-c576e52e819e@simark.ca> (raw)
In-Reply-To: <20190919174941.A0037D80287@oc3748833570.ibm.com>
On 2019-09-19 1:49 p.m., Ulrich Weigand wrote:
> I just noticed that the MAINTAINERS entry is obsolete, then.
> In some cases, we've simply removed those when removing a target,
> but in others they were marked "Deleted". What should we do here?
Personally, I don't think it's particularly useful to keep these deleted
entries in the maintainers file. For documentation and information purposes,
we could have a list of architectures that GDB supports right now and has
supported in the past (maybe we already have that in the doc?), but the
maintainers file doesn't seem appropriate for this.
Simon
next prev parent reply other threads:[~2019-09-20 1:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-06 16:33 Ulrich Weigand
2019-09-09 18:03 ` Tom Tromey
2019-09-19 17:49 ` Ulrich Weigand
2019-09-19 18:09 ` Eli Zaretskii
2019-09-20 1:47 ` Simon Marchi [this message]
2019-09-20 21:11 ` Ulrich Weigand
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=1f8e7325-4ad5-7709-40e4-c576e52e819e@simark.ca \
--to=simark@simark.ca \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=tom@tromey.com \
--cc=uweigand@de.ibm.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