From: Gerald Pfeifer <gerald@pfeifer.com>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: wwwdocs: Some release notes for powerpc for GCC 8
Date: Tue, 06 Feb 2018 21:26:00 -0000 [thread overview]
Message-ID: <alpine.LSU.2.21.1802060906060.13842@anthias.pfeifer.com> (raw)
In-Reply-To: <20180201170335.GD21977@gate.crashing.org>
On Thu, 1 Feb 2018, Segher Boessenkool wrote:
>> Just the move of <!-- <h3 id="nvptx">NVPTX</h3> --> seems
>> unclear to me? Can you omit that?
> The entries are alphabetic, except that one. Should have put it in
> a separate patch, sorry.
Actually it was fine as I just realize.
I got confused by hppa and nvptx (which is sorted properly) vs
PA-RISC and NVPTX (which is not). Obviously we should sort by
what folks see, not the HTML IDs. Sorry about the confusion.
Gerald
prev parent reply other threads:[~2018-02-06 21:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-01 13:34 Segher Boessenkool
2018-02-01 16:07 ` Gerald Pfeifer
2018-02-01 17:03 ` Segher Boessenkool
2018-02-06 21:26 ` 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.21.1802060906060.13842@anthias.pfeifer.com \
--to=gerald@pfeifer.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=segher@kernel.crashing.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).