From: Roland McGrath <roland@redhat.com>
To: Steven Munroe <munroesj@us.ibm.com>
Cc: GNU libc hacker <libc-hacker@sources.redhat.com>
Subject: Re: sysdeps/generic changes
Date: Fri, 23 Dec 2005 05:10:00 -0000 [thread overview]
Message-ID: <20051223051053.9A2111809B6@magilla.sf.frob.com> (raw)
In-Reply-To: Steven Munroe's message of Thursday, 22 December 2005 23:45:41 -0600 <43AB8F05.1040800@us.ibm.com>
I've checked in a better fix. That is a real subtle situation using
#include_next, and I don't think we have others susceptible to quite the
same issue. But folks should be on the lookout for include file orders that
changed.
Thanks,
Roland
prev parent reply other threads:[~2005-12-23 5:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-22 1:15 Roland McGrath
2005-12-23 4:49 ` Steven Munroe
2005-12-23 5:10 ` 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=20051223051053.9A2111809B6@magilla.sf.frob.com \
--to=roland@redhat.com \
--cc=libc-hacker@sources.redhat.com \
--cc=munroesj@us.ibm.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).