public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Simon Marchi <simark@simark.ca>
To: Christian Biesinger <cbiesinger@google.com>,
	Simon Marchi <simon.marchi@efficios.com>
Cc: gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH 0/7] Remove obsolete GDBserver ports
Date: Thu, 14 May 2020 15:12:24 -0400	[thread overview]
Message-ID: <ad4f69c9-7bde-f32c-b5b2-0561032ab280@simark.ca> (raw)
In-Reply-To: <CAPTJ0XF8Uo_exCqnSwFE0iumFusuj_ruobQ6bQ9tHMeALUdhow@mail.gmail.com>

On 2020-05-14 3:07 p.m., Christian Biesinger via Gdb-patches wrote:
> On Thu, May 14, 2020 at 12:44 PM Simon Marchi via Gdb-patches
> <gdb-patches@sourceware.org> wrote:
>>
>> This series implements the removal of obsolete gdbserver ports, as discussed
>> here:
>>
>>     https://sourceware.org/pipermail/gdb-patches/2020-May/168361.html
>>
>> I'm not in a hurry to merge this.  I don't recall the exact process for
>> removing support for a platform/architecture from GDB/GDBserver (I could
>> document it on the wiki if someone points me to it, if it's not already there).
>> If needed, we can announce these ports as deprecated for the next GDB release
>> (10.1 ?), and then merge this series in master right after we have created the
>> gdb-10-branch.  Or if you think this is unnecessary, we can merge it right
>> away, I don't mind.
> 
> I support removal of Lynx/Neutrino/WinCE, and have no opinion on the
> others. However, shouldn't there be a NEWS entry for this?

You are right, I'll send a 8/7 patch for that.

> Also, I didn't notice which patch changed gdbserver/README as per the
> diffstat, did I just miss that?

Patches 3, 4, and 5.  But that will go away if this other patch goes in first, which
would be preferable.

https://sourceware.org/pipermail/gdb-patches/2020-May/168523.html

Simon


  reply	other threads:[~2020-05-14 19:12 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-14 17:43 Simon Marchi
2020-05-14 17:43 ` [PATCH 1/7] gdbserver: remove support for LynxOS Simon Marchi
2020-05-14 17:43 ` [PATCH 2/7] gdbserver: remove support for Neutrino Simon Marchi
2020-05-14 17:43 ` [PATCH 3/7] gdbserver: remove support for Blackfin Simon Marchi
2020-05-14 17:43 ` [PATCH 4/7] gdbserver: remove support for CRIS Simon Marchi
2020-05-14 17:43 ` [PATCH 5/7] gdbserver: remove support for M32R Simon Marchi
2020-05-14 17:43 ` [PATCH 6/7] gdbserver: remove support for Tile Simon Marchi
2020-05-14 18:59 ` [PATCH 0/7] Remove obsolete GDBserver ports Kevin Buettner
2020-05-14 19:12   ` Simon Marchi
2020-05-14 19:05 ` [PATCH 7/7] gdbserver: remove support for ARM/WinCE Simon Marchi
2020-05-14 20:30   ` Kevin Buettner
2020-05-14 23:14     ` Simon Marchi
2020-05-15  1:03       ` Kevin Buettner
2020-05-15 11:09   ` Pedro Alves
2020-05-14 19:07 ` [PATCH 0/7] Remove obsolete GDBserver ports Christian Biesinger
2020-05-14 19:12   ` Simon Marchi [this message]
2020-05-14 19:18 ` [PATCH 8/7] gdb: mention removed GDBserver host support in NEWS Simon Marchi
2020-05-14 19:21   ` Eli Zaretskii
2020-05-15 10:19 ` [PATCH 0/7] Remove obsolete GDBserver ports Pedro Alves
2020-05-15 14:18   ` Simon Marchi
2020-06-12 20:08 ` Simon Marchi

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=ad4f69c9-7bde-f32c-b5b2-0561032ab280@simark.ca \
    --to=simark@simark.ca \
    --cc=cbiesinger@google.com \
    --cc=gdb-patches@sourceware.org \
    --cc=simon.marchi@efficios.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).