From: "Eli Zaretskii" <eliz@gnu.org>
To: Andrew Cagney <cagney@gnu.org>
Cc: kettenis@gnu.org, brobecker@gnat.com, gdb-patches@sources.redhat.com
Subject: Re: [patch] Deprecate XM_FILE and TM_FILE
Date: Sun, 12 Sep 2004 18:36:00 -0000 [thread overview]
Message-ID: <01c498f7$Blat.v2.2.2$53c9e1a0@zahav.net.il> (raw)
In-Reply-To: <41448FBF.50009@gnu.org> (message from Andrew Cagney on Sun, 12 Sep 2004 14:04:47 -0400)
> Date: Sun, 12 Sep 2004 14:04:47 -0400
> From: Andrew Cagney <cagney@gnu.org>
> Cc: Mark Kettenis <kettenis@gnu.org>, brobecker@gnat.com,
> gdb-patches@sources.redhat.com
>
> I think this debate is over the point at which something can be deprecated.
It's about a point where something can be deprecated, and also about
the conditions that should be fulfilled for that.
> For GDB, as soon as we've got the new mechanism up and running -
> confirming its ok - we're going to draw a line and deprecate the old
> mechanisms. We're not going to require that every single detail of
> every single dependant variant also be addressed.
I don't know about ``we'', but as far as I'm concerned, I cannot
approve a patch that deprecates XM_FILE as long as the 3 defines in
xm-go32.h are not set by an alternative non-deprecated mechanism.
> > We can easily do that (and actually do that) by rejecting patches that
> > use the old mechanism.
>
> We don't.
Yes, we do. You can find examples of that in the archives, including
messages by yourself.
> In the past, requests to not use old mechanisms have been [er]
> declined
If such a request is declined, we can reject the patch. I don't see a
problem here.
Anyway, this is all have been beaten to death in this thread, we are
just reiterating the same issues again and again. I already suggested
a constructive (IMHO) approach, and I don't have anything new to add
to it.
next prev parent reply other threads:[~2004-09-12 18:36 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
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 [this message]
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='01c498f7$Blat.v2.2.2$53c9e1a0@zahav.net.il' \
--to=eliz@gnu.org \
--cc=brobecker@gnat.com \
--cc=cagney@gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=kettenis@gnu.org \
/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