From: Gerald Pfeifer <gerald@pfeifer.com>
To: Kyrill Tkachov <kyrylo.tkachov@foss.arm.com>
Cc: gcc-patches@gcc.gnu.org,
James Greenhalgh <james.greenhalgh@arm.com>,
nd@arm.com
Subject: Re: [PATCH][wwwdocs] Improve arm and aarch64-related info in readings.html
Date: Sun, 29 May 2016 07:59:00 -0000 [thread overview]
Message-ID: <alpine.LSU.2.20.1605282201240.2874@anthias.pfeifer.com> (raw)
In-Reply-To: <573DDB63.40101@foss.arm.com>
Hi Kyrill,
On Thu, 19 May 2016, Kyrill Tkachov wrote:
> I noticed that we have a readings.html page that has pointers to
> documentation of various backends that GCC supports. The info on arm
> seems a bit out of date and somewhat confusing, and there is no entry
> for aarch64. This patch tries to address that.
I see you have not applied this yet. In case you were waiting
for any further approvals beyond James': (a) His is sufficient
for doc and web pages around AArch64, and (b) I agree, too. :-)
Gerald
next prev parent reply other threads:[~2016-05-28 20:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-19 15:27 Kyrill Tkachov
2016-05-23 8:56 ` James Greenhalgh
2016-05-29 7:59 ` Gerald Pfeifer [this message]
2016-05-31 10:10 ` Kyrill Tkachov
2016-06-02 9:29 ` Kyrill Tkachov
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.1605282201240.2874@anthias.pfeifer.com \
--to=gerald@pfeifer.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=james.greenhalgh@arm.com \
--cc=kyrylo.tkachov@foss.arm.com \
--cc=nd@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).