From: Tom Tromey <tromey@redhat.com>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: Eli Zaretskii <eliz@gnu.org>, gdb-patches@sourceware.org
Subject: Re: NAT_FILE set incorrectly in gdb/Makefile
Date: Mon, 20 Apr 2009 17:09:00 -0000 [thread overview]
Message-ID: <m3skk345hm.fsf@fleche.redhat.com> (raw)
In-Reply-To: <m2r5zoz5rq.fsf@igel.home> (Andreas Schwab's message of "Sun\, 19 Apr 2009 23\:35\:05 +0200")
>>>>> "Andreas" == Andreas Schwab <schwab@linux-m68k.org> writes:
Andreas> 2009-04-19 Andreas Schwab <schwab@linux-m68k.org>
Andreas> * configure.ac: Only postprocess Makefile when it has just been
Andreas> generated; avoid changequote.
This all seems like overkill to get a single variable that is only
used (AFAICT) in the TAGS rule. Couldn't we just compute the real
value in the Makefile somehow, rather than a rewrite?
But, given how minor this is, if you'd rather move forward this way,
then this patch is ok if it works.
Tom
next prev parent reply other threads:[~2009-04-20 17:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-19 19:00 Eli Zaretskii
2009-04-19 21:35 ` Andreas Schwab
2009-04-20 17:09 ` Tom Tromey [this message]
2009-04-20 21:29 ` Andreas Schwab
2009-04-21 18:25 ` Tom Tromey
2009-04-20 18:58 ` 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=m3skk345hm.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=schwab@linux-m68k.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