From: DJ Delorie <dj@redhat.com>
To: aaronavay62@aaronwl.com
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PING] Windows patches.
Date: Mon, 25 Oct 2004 19:19:00 -0000 [thread overview]
Message-ID: <200410251858.i9PIw8tQ025887@greed.delorie.com> (raw)
In-Reply-To: <417AB82F.4030405@aaronwl.com> (aaronavay62@aaronwl.com)
> The first patch disables building fixincludes for targets where it
> is not needed. This was done previously, but got lost in the
> fixincludes transition to toplevel. It needs a configury
> maintainer.
Target-specific changes in configury are normally approved by the
target maintainers, not the configury maintainers, as only the target
maintainers know if the change is correct.
next prev parent reply other threads:[~2004-10-25 18:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-23 21:58 Aaron W. LaFramboise
2004-10-24 0:33 ` Tom Tromey
2004-10-25 22:10 ` Aaron W. LaFramboise
2004-10-26 15:42 ` Tom Tromey
2004-10-25 19:19 ` DJ Delorie [this message]
2004-10-25 20:03 ` Aaron W. LaFramboise
2004-10-25 20:25 ` DJ Delorie
2004-10-25 21:12 ` E. Weddington
2004-11-05 19:10 ` Christopher Faylor
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=200410251858.i9PIw8tQ025887@greed.delorie.com \
--to=dj@redhat.com \
--cc=aaronavay62@aaronwl.com \
--cc=gcc-patches@gcc.gnu.org \
/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).