From: Andy Wingo <wingo@pobox.com>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: bug-guile@gnu.org, bug-gnulib@gnu.org, Eric Blake <eblake@redhat.com>
Subject: Re: -Wundef warning in striconveh.h
Date: Thu, 17 Mar 2011 18:03:44 +0100 [thread overview]
Message-ID: <m3oc59znkf.fsf@unquote.localdomain> (raw)
In-Reply-To: <4D8233A6.3090201@cs.ucla.edu> (Paul Eggert's message of "Thu, 17 Mar 2011 09:15:34 -0700")
On Thu 17 Mar 2011 17:15, Paul Eggert <eggert@cs.ucla.edu> writes:
> On 03/17/2011 07:46 AM, Andy Wingo wrote:
>> Can you consider changing this one header file? It does not sound like
>> an issue on which it is fruitful to be stubborn.
>
> Well, there is a bit of stubbornness on both sides here, no? :-)
Hehe, point taken. I wouldn't have bothered you, but my users keep
compiling with that and -Werror... they are the stubborn ones! :)
Cheers,
Andy
--
http://wingolog.org/
next prev parent reply other threads:[~2011-03-17 17:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-17 10:20 -Wundef warning in striconveh.h Andy Wingo
2011-03-17 14:05 ` Eric Blake
2011-03-17 14:46 ` Andy Wingo
2011-03-17 16:15 ` Paul Eggert
2011-03-17 17:03 ` Andy Wingo [this message]
2011-04-25 21:35 ` Ludovic Courtès
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3oc59znkf.fsf@unquote.localdomain \
--to=wingo@pobox.com \
--cc=bug-gnulib@gnu.org \
--cc=bug-guile@gnu.org \
--cc=eblake@redhat.com \
--cc=eggert@cs.ucla.edu \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).