From: "Eli Zaretskii" <eliz@gnu.org>
To: Russell Shaw <rjshaw@netspace.net.au>
Cc: gdb@sources.redhat.com
Subject: Re: Unfinished projects
Date: Fri, 15 Apr 2005 09:04:00 -0000 [thread overview]
Message-ID: <01c54199$Blat.v2.4$8b8247e0@zahav.net.il> (raw)
In-Reply-To: <425F1E4F.2030805@netspace.net.au> (message from Russell Shaw on Fri, 15 Apr 2005 11:52:15 +1000)
> Date: Fri, 15 Apr 2005 11:52:15 +1000
> From: Russell Shaw <rjshaw@netspace.net.au>
> Cc: gdb@sources.redhat.com
>
> I'd create a new gdb copy that only has the maintained stuff in it
No, please let's not do it. There's no reason to abruptly discontinue
support for configurations that still build and work, even if they use
some deprecated code.
next prev parent reply other threads:[~2005-04-15 9:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-14 18:55 Stan Shebs
2005-04-14 19:01 ` Daniel Jacobowitz
2005-04-14 22:03 ` Stan Shebs
2005-04-14 21:49 ` Mark Kettenis
2005-04-15 1:48 ` Russell Shaw
2005-04-15 9:04 ` Eli Zaretskii [this message]
2005-04-15 8:50 ` Eli Zaretskii
2005-04-15 17:47 ` Andrew Cagney
2005-04-15 18:37 ` Stan Shebs
2005-04-15 18:52 ` Alain Magloire
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='01c54199$Blat.v2.4$8b8247e0@zahav.net.il' \
--to=eliz@gnu.org \
--cc=gdb@sources.redhat.com \
--cc=rjshaw@netspace.net.au \
/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