From: Gerald Pfeifer <gerald@pfeifer.com>
To: James Greenhalgh <james.greenhalgh@arm.com>
Cc: Kyrill Tkachov <kyrylo.tkachov@arm.com>, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH][wwwdocs] Mention native CPU detection in aarch64 notes for GCC 6
Date: Thu, 02 Feb 2017 21:46:00 -0000 [thread overview]
Message-ID: <alpine.LSU.2.20.1702022243080.2585@anthias.pfeifer.com> (raw)
In-Reply-To: <20150526100036.GE23464@arm.com>
On Tue, 26 May 2015, James Greenhalgh wrote:
> I think I remember Gerald saying in the past that it is within the
> remit of port maintainers/reviewers to OK these, but be ready to
> revert or update it if I am wrong!
You were (and are) very much quite right, James. :-)
(And given that Gerald is not always able to respond as quickly as
he'd like, this mail being a "nice" example, this just makes sense.)
Gerald
prev parent reply other threads:[~2017-02-02 21:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-19 10:17 Kyrill Tkachov
2015-05-26 10:32 ` James Greenhalgh
2017-02-02 21:46 ` Gerald Pfeifer [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=alpine.LSU.2.20.1702022243080.2585@anthias.pfeifer.com \
--to=gerald@pfeifer.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=james.greenhalgh@arm.com \
--cc=kyrylo.tkachov@arm.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).