From: "Eli Zaretskii" <eliz@is.elta.co.il>
To: ac131313@cygnus.com
Cc: gdb@sources.redhat.com
Subject: Re: [rfc] maint note on obsoleting code
Date: Tue, 29 Jan 2002 10:09:00 -0000 [thread overview]
Message-ID: <1659-Tue29Jan2002200739+0200-eliz@is.elta.co.il> (raw)
In-Reply-To: <3C56CECC.7040102@cygnus.com> (message from Andrew Cagney on Tue, 29 Jan 2002 11:33:16 -0500)
> Date: Tue, 29 Jan 2002 11:33:16 -0500
> From: Andrew Cagney <ac131313@cygnus.com>
>
> @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?
It's okay with me.
prev parent reply other threads:[~2002-01-29 18:09 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
2002-01-29 10:09 ` Eli Zaretskii [this message]
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=1659-Tue29Jan2002200739+0200-eliz@is.elta.co.il \
--to=eliz@is.elta.co.il \
--cc=ac131313@cygnus.com \
--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