From: "Eli Zaretskii" <eliz@gnu.org>
To: Andrew Cagney <cagney@gnu.org>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [patch] Deprecate XM_FILE and TM_FILE
Date: Thu, 09 Sep 2004 21:15:00 -0000 [thread overview]
Message-ID: <01c496b2$Blat.v2.2.2$22c509a0@zahav.net.il> (raw)
In-Reply-To: <4140BC4C.50003@gnu.org> (message from Andrew Cagney on Thu, 09 Sep 2004 16:25:48 -0400)
> Date: Thu, 09 Sep 2004 16:25:48 -0400
> From: Andrew Cagney <cagney@gnu.org>
> Cc: gdb-patches@sources.redhat.com
>
> > Deprecating XM_FILE means it will be deleted in the next major
> > release. So I'm complaining now to prevent the more-or-less automatic
> > deletion of anything that matches the regexp "deprecated.*"
> > (case-insensitively) in the near future, when it would be too late to
> > complain.
>
> This isn't correct.
>
> Deprecating something does not mean that it will automatically be
> deleted in the next major release. We've still got stuff that was
> deprecated in '99!
That might be so, but I've seen too many "Garbage collect FOO"
messages lately to know that, following every release, many deprecated
features get eliminated in patches treated as obvious, with no
discussion.
> Java defines deprecation as:
Andrew, can you please stop patronizing me? I think I understand
English well enough to not need such lectures!
> How about we get this in, and then I'll follow up (by 6.3) with patches
> to finish this (as I said, I suspect I'll be doing the dirty work).
As I said already, several times, I'd like the replacement to go in
either before or together with this patch, not after.
next prev parent reply other threads:[~2004-09-09 21:15 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-02 18:30 Andrew Cagney
2004-09-02 20:26 ` Eli Zaretskii
2004-09-03 16:18 ` Andrew Cagney
2004-09-04 12:00 ` Eli Zaretskii
2004-09-04 14:27 ` Andrew Cagney
2004-09-04 16:28 ` Eli Zaretskii
2004-09-04 23:20 ` Andrew Cagney
2004-09-05 4:17 ` Eli Zaretskii
2004-09-09 16:05 ` Andrew Cagney
2004-09-09 19:31 ` Eli Zaretskii
2004-09-09 20:26 ` Andrew Cagney
2004-09-09 21:15 ` Eli Zaretskii [this message]
2004-09-09 21:26 ` Joel Brobecker
2004-09-10 9:35 ` Eli Zaretskii
2004-09-10 12:41 ` Mark Kettenis
2004-09-10 16:32 ` Eli Zaretskii
2004-09-12 18:07 ` Andrew Cagney
2004-09-12 18:36 ` Eli Zaretskii
2004-09-13 15:35 ` Andrew Cagney
2004-09-13 19:48 ` Eli Zaretskii
2004-09-13 21:07 ` Andrew Cagney
2004-09-13 21:30 ` Joel Brobecker
2004-09-24 22:06 ` Andrew Cagney
2004-09-15 12:15 ` Eli Zaretskii
2004-09-15 15:54 ` Andrew Cagney
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='01c496b2$Blat.v2.2.2$22c509a0@zahav.net.il' \
--to=eliz@gnu.org \
--cc=cagney@gnu.org \
--cc=gdb-patches@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