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/107643] [13 Regression] sphix generated indexes are not working at all Date: Fri, 11 Nov 2022 16:44:02 +0000 [thread overview] Message-ID: <bug-107643-4-q1JWIMyDHW@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-107643-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107643 --- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> --- I had used these to find the options and other keywords for GCC 12 manual all the time. Because searching to find the right page is hard. Especially if it is 2 layers down.
next prev parent reply other threads:[~2022-11-11 16:44 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-11-11 16:41 [Bug web/107643] New: " pinskia at gcc dot gnu.org 2022-11-11 16:42 ` [Bug web/107643] " pinskia at gcc dot gnu.org 2022-11-11 16:44 ` pinskia at gcc dot gnu.org [this message] 2022-11-13 10:45 ` [Bug web/107643] [13 Regression] sphinx " marxin at gcc dot gnu.org 2022-11-13 10:46 ` marxin at gcc dot gnu.org 2022-11-13 10:46 ` marxin at gcc dot gnu.org 2022-11-13 11:49 ` pinskia at gcc dot gnu.org 2022-11-13 11:50 ` pinskia at gcc dot gnu.org 2022-11-13 13:57 ` marxin at gcc dot gnu.org 2022-11-13 15:41 ` cvs-commit at gcc dot gnu.org 2022-11-13 15:41 ` marxin at gcc dot gnu.org 2022-11-13 17:41 ` pinskia at gcc dot gnu.org 2022-11-13 17:42 ` pinskia at gcc dot gnu.org 2022-11-13 18:20 ` marxin at gcc dot gnu.org 2022-11-13 18:34 ` pinskia at gcc dot gnu.org 2022-11-13 19:00 ` marxin at gcc dot gnu.org 2022-11-14 8:44 ` [Bug web/107643] [13 Regression] sphinx Index should be added to the top-level TOC 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-107643-4-q1JWIMyDHW@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: linkBe 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).