From: Andrew Cagney <cagney@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [patch] Deprecate XM_FILE and TM_FILE
Date: Sat, 04 Sep 2004 23:20:00 -0000 [thread overview]
Message-ID: <413A277E.3060700@gnu.org> (raw)
In-Reply-To: <01c4929c$Blat.v2.2.2$3333c200@zahav.net.il>
> Calling something ``deprecated'' means that it will go away in a
> future release. When XM_FILE goes away, xm-go32.h will no longer be
> doing its job, and the DJGPP port of GDB will be severely broken.
> Therefore, deprecating XM_FILE means you are deprecating the DJGPP
> port.
Eli, sorry I'm still lost.
Here, the xm-go32.h file will have been removed before the XM_FILE
mechanism goes away (if it hasn't we've both seriously fallen down on
the job :-) and therefore, DJGPP won't be broken. In fact, thanks to
Joel's and MarkK's efforts, we're even ahead of schedule on this one!
This is all about preventing new uses of an old mechanism that we're
trying to replace, not about deprecating DJGPP.
Andrew
next prev parent reply other threads:[~2004-09-04 23:20 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 [this message]
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
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=413A277E.3060700@gnu.org \
--to=cagney@gnu.org \
--cc=eliz@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