public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Mark Wielaard <mark@klomp.org>
To: Tom Tromey <tom@tromey.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFC] Deprecate stabs
Date: Sun, 12 Feb 2023 13:53:29 +0100	[thread overview]
Message-ID: <20230212125329.GI2430@gnu.wildebeest.org> (raw)
In-Reply-To: <87a61lgcor.fsf@tromey.com>

Hi Tom,

On Fri, Feb 10, 2023 at 07:26:12PM -0700, Tom Tromey wrote:
> Finally, deprecation serves the purpose of announcing our intent.  Maybe
> someone will step up to maintain this code, in which case we can keep
> it.  In this scenario, I would be ok with treating it like the
> un-maintained *-nat code -- we'll try to keep it building but testing
> and fixing it is up to the maintainer.
> 
> If/when this goes in, I'll send a deprecation announcement to the gdb
> list, in case there is some such person who can be flushed out of the
> cobwebs.

I like this approach. It would be good to announce this asap, so
people who do actually use stabs and care about improving, testing and
maintaining support can step up. And if nobody does then the code can
be removed totally unused/unmaintained in the next release.

Thanks,

Mark

  parent reply	other threads:[~2023-02-12 12:53 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-19 17:41 Tom Tromey
2023-01-19 18:00 ` Eli Zaretskii
2023-01-20 12:48   ` Mark Wielaard
2023-01-20 13:47     ` Eli Zaretskii
2023-02-11  2:26       ` Tom Tromey
2023-02-11  8:29         ` Eli Zaretskii
2023-02-14 16:36           ` Simon Marchi
2023-02-12 12:53         ` Mark Wielaard [this message]
2023-07-06 17:44 ` Pedro Alves
2023-08-30 17:48   ` Tom Tromey
2023-08-30 17:58     ` Eli Zaretskii
2023-08-30 19:15     ` Kevin Buettner
2023-08-30 20:47     ` John Baldwin

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=20230212125329.GI2430@gnu.wildebeest.org \
    --to=mark@klomp.org \
    --cc=gdb-patches@sourceware.org \
    --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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).