From: Daniel Jacobowitz <drow@false.org>
To: Hans-Peter Nilsson <hans-peter.nilsson@axis.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA:] sim/common/aclocal.m4: correct duplicate arg test for --enable-sim-hardware=...
Date: Wed, 29 Mar 2006 15:49:00 -0000 [thread overview]
Message-ID: <20060329005447.GA15803@nevyn.them.org> (raw)
In-Reply-To: <200603290027.k2T0RTJd032068@ignucius.se.axis.com>
On Wed, Mar 29, 2006 at 02:27:29AM +0200, Hans-Peter Nilsson wrote:
> Yeah, that would seem the obvious correction if there isn't a
> "x" to remove. Ha! Consider it done as such! :-)
That version's OK.
> Ok then, it's just that the previous author didn't think so, and
> so I thought maybe there was a reason for that.
Lots of people do this out of paranoia, since they get bit by the
Makefile version, I think.
> It's moot now, but that's was the point, as I also mentioned!
Ah, this wasn't explained enough for me, and I misread where the comma
was. I see now.
--
Daniel Jacobowitz
CodeSourcery
prev parent reply other threads:[~2006-03-29 0:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-26 8:15 Hans-Peter Nilsson
2006-03-28 22:40 ` Daniel Jacobowitz
2006-03-29 15:43 ` Hans-Peter Nilsson
2006-03-29 15:49 ` Daniel Jacobowitz [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=20060329005447.GA15803@nevyn.them.org \
--to=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=hans-peter.nilsson@axis.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