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: Fri, 03 Sep 2004 11:17:00 -0000 [thread overview]
Message-ID: <01c491a7$Blat.v2.2.2$8cce1ae0@zahav.net.il> (raw)
In-Reply-To: <41379AC6.90605@gnu.org> (message from Andrew Cagney on Thu, 02 Sep 2004 18:12:22 -0400)
> Date: Thu, 02 Sep 2004 18:12:22 -0400
> From: Andrew Cagney <cagney@gnu.org>
>
> Many of the still existing TM files (the others are done for
> consistency) are just acting as an indirect include of another file.
> For instance, tm-nbsd.h #includes "solib.h". This patch tweaks
> configure.in so that a TM_FILE can explicitly specify any file (instead
> of having to pull it in via an #include) - that lets us eliminate both
> the indirection and the unnecessary config file.
Perhaps we should rename TM_FILE to something like TM_INCLUDE, then.
Btw, did we decide upon all these recent changes against *_FILE
thingies? They aren't exactly obvious, so I'd expect them to be
posted as RFA's, at the least.
next prev parent reply other threads:[~2004-09-03 11:17 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 [this message]
2004-09-03 16:39 ` Andrew Cagney
2004-09-04 11:42 ` Eli Zaretskii
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='01c491a7$Blat.v2.2.2$8cce1ae0@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