public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug web/107651] Having two different kind of indexes is very useful still
Date: Sun, 13 Nov 2022 12:05:28 +0000 [thread overview]
Message-ID: <bug-107651-4-HtYCOoQivc@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107651-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107651
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|INVALID |---
Status|RESOLVED |NEW
Ever confirmed|0 |1
Last reconfirmed| |2022-11-13
--- Comment #3 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Your index page has both options and symbols intermixed and not two different
pages. Funny how you said one thing and it is exact opposite.
Also that page is not linked anywhere from the site.
Oh also the formatting on some of things looks off. Look at x86 and you will
see what I am talking about.
next prev parent reply other threads:[~2022-11-13 12:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-11 21:04 [Bug web/107651] New: " pinskia at gcc dot gnu.org
2022-11-11 21:06 ` [Bug web/107651] " pinskia at gcc dot gnu.org
2022-11-13 10:53 ` marxin at gcc dot gnu.org
2022-11-13 12:05 ` pinskia at gcc dot gnu.org [this message]
2022-11-13 12:08 ` pinskia at gcc dot gnu.org
2022-11-13 12:43 ` pinskia at gcc dot gnu.org
2022-11-13 12:48 ` pinskia at gcc dot gnu.org
2022-11-13 13:51 ` marxin at gcc dot gnu.org
2022-11-13 13:53 ` marxin at gcc dot gnu.org
2022-11-13 19:15 ` pinskia at gcc dot gnu.org
2022-11-13 19:24 ` marxin at gcc dot gnu.org
2022-11-13 19:36 ` pinskia at gcc dot gnu.org
2022-11-13 19:39 ` pinskia at gcc dot gnu.org
2022-11-14 8:43 ` marxin at gcc dot gnu.org
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=bug-107651-4-HtYCOoQivc@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).