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: Thu, 09 Sep 2004 19:19:00 -0000 [thread overview]
Message-ID: <01c496a1$Blat.v2.2.2$c9ea67e0@zahav.net.il> (raw)
In-Reply-To: <414073FE.90601@gnu.org> (message from Andrew Cagney on Thu, 09 Sep 2004 11:17:18 -0400)
> Date: Thu, 09 Sep 2004 11:17:18 -0400
> From: Andrew Cagney <cagney@gnu.org>
> Cc: gdb-patches@sources.redhat.com
>
> I've now prototyped this change vis:
> TM_FILE -> TM_INCLUDE
> NAT_FILE -> NM_INCLUDE (for consistency)
> XM_FILE -> XM_INCLUDE
> and found that it didn't help.
>
> TM_FILE specifies the name of the file that is linked to "tm.h". My
> patch does not change this. It just removes a restriction on what could
> be specified for that file.
I still don't see why TM_INCLUDE isn't a better name, but if you feel
strongly about keeping the current name, I won't object. TM_INCLUDE
was just a suggestion, anyway.
prev parent reply other threads:[~2004-09-09 19:19 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
2004-09-09 15:17 ` Andrew Cagney
2004-09-09 19:19 ` Eli Zaretskii [this message]
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='01c496a1$Blat.v2.2.2$c9ea67e0@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