From: "Eli Zaretskii" <eliz@gnu.org>
To: Joel Brobecker <brobecker@gnat.com>
Cc: cagney@gnu.org, gdb-patches@sources.redhat.com
Subject: Re: [patch] Deprecate XM_FILE and TM_FILE
Date: Fri, 10 Sep 2004 09:35:00 -0000 [thread overview]
Message-ID: <01c49718$Blat.v2.2.2$de0204a0@zahav.net.il> (raw)
In-Reply-To: <20040909212638.GI5843@gnat.com> (message from Joel Brobecker on Thu, 9 Sep 2004 14:26:38 -0700)
> Date: Thu, 9 Sep 2004 14:26:38 -0700
> From: Joel Brobecker <brobecker@gnat.com>
> Cc: Andrew Cagney <cagney@gnu.org>, gdb-patches@sources.redhat.com
>
> > 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.
>
> As much as I find Andrew's methods sometimes too brutal for me, I have
> to recognize that I don't remember him deliberately breaking a port
> just because he wanted to remove something that has been deprecated.
> I think we can trust him in not doing so without discussing it beforehand.
This was never about Andrew's malicious intent or distrusting his
motives. I don't think I said anything to that effect, but if I did,
I sincerely apologize, because I never meant to imply anything like
that.
As far as I'm concerned, the discussion is strictly technical, it's
not about motives. I trust Andrew's motives at least as much as you
or anyone else does.
> Also, I don't think Andrew is using the "obvious" rule here. The patches
> are nowhere near obvious, I agree. He's using the global maintainer
> priviledge.
I'm not against the priviledges nor about Andrew's right to use them.
I'm against deprecating a feature that is being used by a maintained
port before introducing alternative mechanisms that replace the
feature being deprecated.
next prev parent reply other threads:[~2004-09-10 9:35 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
2004-09-09 21:26 ` Joel Brobecker
2004-09-10 9:35 ` Eli Zaretskii [this message]
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='01c49718$Blat.v2.2.2$de0204a0@zahav.net.il' \
--to=eliz@gnu.org \
--cc=brobecker@gnat.com \
--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