From: Jeff Law <law@redhat.com>
To: Gerald Pfeifer <gerald@pfeifer.com>,
Richard Biener <richard.guenther@gmail.com>
Cc: Ramana Radhakrishnan <ramana.radhakrishnan@foss.arm.com>,
Andreas Tobler <andreast@gcc.gnu.org>,
gcc-patches@gcc.gnu.org
Subject: Re: Updating config.guess
Date: Mon, 13 Mar 2017 15:33:00 -0000 [thread overview]
Message-ID: <9c0d5e6f-a31b-e6be-2afb-288236dc40b7@redhat.com> (raw)
In-Reply-To: <alpine.LSU.2.20.1703072100420.3498@anthias.pfeifer.com>
On 03/07/2017 01:01 PM, Gerald Pfeifer wrote:
> On Tue, 7 Mar 2017, Jeff Law wrote:
>>> When/if this has been accepted, is it okay to pull the latest config.guess
>>> into GCC even at this stage of the release process? (We're only looking
>>> at this change and the addition of nsx-tandem compared to what we have
>>> right now.)
>> If it's just those, I'd think it'd be reasonable.
>
> Here is the entire difference between the config.guess we have
> and upstream.
>
Yea, fine with me.
Jeff
next prev parent reply other threads:[~2017-03-13 15:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-23 9:17 [Patch wwwdocs] Add aarch64-none-linux-gnu as a primary platform for GCC-7 Ramana Radhakrishnan
2016-05-23 9:26 ` Richard Biener
2016-05-23 15:47 ` Jeff Law
2016-05-23 22:21 ` Gerald Pfeifer
2016-05-24 9:01 ` Richard Biener
2017-03-04 16:40 ` i386-unknown-freebsd -> i586-unknown-freebsd (was: [Patch wwwdocs] Add aarch64-none-linux-gnu as a primary platform for GCC-7) Gerald Pfeifer
2017-03-07 16:34 ` i386-unknown-freebsd -> i586-unknown-freebsd Jeff Law
2017-03-07 20:01 ` Updating config.guess (was: i386-unknown-freebsd -> i586-unknown-freebsd) Gerald Pfeifer
2017-03-13 15:33 ` Jeff Law [this message]
2017-03-18 18:23 ` Updating config.guess Gerald Pfeifer
2017-03-04 16:45 ` i386-unknown-freebsd -> i586-unknown-freebsd (was: [Patch wwwdocs] Add aarch64-none-linux-gnu as a primary platform for GCC-7) Gerald Pfeifer
2017-03-07 16:33 ` i386-unknown-freebsd -> i586-unknown-freebsd Jeff Law
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=9c0d5e6f-a31b-e6be-2afb-288236dc40b7@redhat.com \
--to=law@redhat.com \
--cc=andreast@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=gerald@pfeifer.com \
--cc=ramana.radhakrishnan@foss.arm.com \
--cc=richard.guenther@gmail.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).