From: Mark Mitchell <mark@codesourcery.com>
To: Fergus Henderson <fjh@cs.mu.OZ.AU>,
Zack Weinberg <zack@codesourcery.com>
Cc: "gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: Re: Backport 'cpp include directory search order warning' patch to 3.2.1?
Date: Sun, 29 Sep 2002 23:07:00 -0000 [thread overview]
Message-ID: <18310000.1033351649@warlock.codesourcery.com> (raw)
In-Reply-To: <20020930014222.GA11040@ceres.cs.mu.oz.au>
--On Monday, September 30, 2002 11:42:22 AM +1000 Fergus Henderson
<fjh@cs.mu.OZ.AU> wrote:
> On 29-Sep-2002, Zack Weinberg <zack@codesourcery.com> wrote:
>> I'd like to propose John's patch to squelch the 'cpp: changing search
>> order...' warnings be backported to 3.2.1.
>
> I'd just like to express my support for this proposal.
I agree that this is a good idea. Zack, thanks for volunteering.
--
Mark Mitchell mark@codesourcery.com
CodeSourcery, LLC http://www.codesourcery.com
next prev parent reply other threads:[~2002-09-30 2:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-29 18:42 Zack Weinberg
2002-09-29 19:09 ` John David Anglin
2002-09-29 23:04 ` Fergus Henderson
2002-09-29 23:07 ` Mark Mitchell [this message]
2002-09-30 3:57 ` Gerald Pfeifer
2002-09-30 10:48 ` Zack Weinberg
2002-10-04 12:32 ` Neil Booth
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=18310000.1033351649@warlock.codesourcery.com \
--to=mark@codesourcery.com \
--cc=fjh@cs.mu.OZ.AU \
--cc=gcc@gcc.gnu.org \
--cc=zack@codesourcery.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).