From: Andrew Cagney <ac131313@cygnus.com>
To: Eli Zaretskii <eliz@is.elta.co.il>
Cc: gdb@sources.redhat.com
Subject: Re: [rfc] maint note on obsoleting code
Date: Tue, 29 Jan 2002 08:33:00 -0000 [thread overview]
Message-ID: <3C56CECC.7040102@cygnus.com> (raw)
In-Reply-To: <Pine.SUN.3.91.1020124190727.21049C-100000@is>
> On Thu, 24 Jan 2002, Andrew Cagney wrote:
>
>
>> @emph{Maintainer note: Obsoleting a target or code is actually a good
>> thing.
>
>
> Aren't we supposed to be mightily sad when some target becomes obsolete?
> They mostly do because no one wants to maintain them anymore, a user who
> cannot afford hacking GDB will not be pleased...
It now reads:
@emph{Maintainer note: Removing old code, while regrettable, is a good
thing. Firstly it helps the developers by removing code that is either
no longer relevant or simply wrong. Secondly since it removes any
history associated with the file (effectively clearing the slate) the
developer has a much freer hand when it comes to fixing broken files.}
should it be softened further?
Andrew
next prev parent reply other threads:[~2002-01-29 16:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-24 8:59 Andrew Cagney
2002-01-24 9:09 ` Eli Zaretskii
2002-01-29 8:33 ` Andrew Cagney [this message]
2002-01-29 10:09 ` Eli Zaretskii
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=3C56CECC.7040102@cygnus.com \
--to=ac131313@cygnus.com \
--cc=eliz@is.elta.co.il \
--cc=gdb@sources.redhat.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