From: Roland McGrath <roland@redhat.com>
To: Jakub Jelinek <jakub@redhat.com>
Cc: Ulrich Drepper <drepper@redhat.com>,
Glibc hackers <libc-hacker@sources.redhat.com>
Subject: Re: [PATCH] Uglify function parameter names in installed headers
Date: Mon, 16 Feb 2009 21:04:00 -0000 [thread overview]
Message-ID: <20090216210351.9565EFC3E4@magilla.sf.frob.com> (raw)
In-Reply-To: Jakub Jelinek's message of Monday, 16 February 2009 16:00:41 +0100 <20090216150041.GE16681@sunsite.ms.mff.cuni.cz>
Technically (pedantically) I think it's not necessary to be
macro-namespace-clean in headers that aren't C99 headers. IIRC, POSIX says
that #include's must come first after feature test macros.
That said, I think this is fine to commit.
prev parent reply other threads:[~2009-02-16 21:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-16 14:56 Jakub Jelinek
2009-02-16 18:33 ` Ulrich Drepper
2009-02-16 21:04 ` Roland McGrath [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=20090216210351.9565EFC3E4@magilla.sf.frob.com \
--to=roland@redhat.com \
--cc=drepper@redhat.com \
--cc=jakub@redhat.com \
--cc=libc-hacker@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).