From: "Eli Zaretskii" <eliz@gnu.org>
To: Andrew Cagney <cagney@gnu.org>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [commit] Let {TM,XM,NM}_FILE specify a path
Date: Sat, 04 Sep 2004 11:42:00 -0000 [thread overview]
Message-ID: <01c49274$Blat.v2.2.2$507011c0@zahav.net.il> (raw)
In-Reply-To: <41389DFA.5020104@gnu.org> (message from Andrew Cagney on Fri, 03 Sep 2004 12:38:18 -0400)
> Date: Fri, 03 Sep 2004 12:38:18 -0400
> From: Andrew Cagney <cagney@gnu.org>
> Cc: gdb-patches@sources.redhat.com
>
> > Perhaps we should rename TM_FILE to something like TM_INCLUDE, then.
>
> If you prefer, I can rename it to DEPRECATED_TM_INCLUDE when committing
> my pending deprecation patch.
If we change the functionality of TM_FILE (so it can now name any
file), then it doesn't seem to be deprecated. Thus,
DEPRECATED_TM_INCLUDE seems an inappropriate name to me.
> > Btw, did we decide upon all these recent changes against *_FILE
> > thingies?
>
> Long long ago we decided that GDB would be strictly multi-arch, and
> hence that all tm-*.h files (and TM_FILE hackery) should be deleted.
Perhaps so, but that doesn't make those changes obvious, IMHO. They
should be suggested as RFA's, as we do with any other change whose
idea was approved. The fact that the idea was approved merely means
that there's no need for an RFC. At least that is how I understand
the GDB development and patch-approval process. If I misunderstand,
please point me to the text that says otherwise.
> If you prefer I can delete the tm-*.h files and TM_FILE configury outright.
If this was a joke, then I'm not amused.
next prev parent reply other threads:[~2004-09-04 11:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-02 22:13 Andrew Cagney
2004-09-03 11:17 ` Eli Zaretskii
2004-09-03 16:39 ` Andrew Cagney
2004-09-04 11:42 ` Eli Zaretskii [this message]
2004-09-09 15:17 ` Andrew Cagney
2004-09-09 19:19 ` Eli Zaretskii
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='01c49274$Blat.v2.2.2$507011c0@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