public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ebotcazou at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/107634] Very long filenames and URLs for sphinx-based docs
Date: Sat, 12 Nov 2022 08:11:43 +0000 [thread overview]
Message-ID: <bug-107634-4-3bXBZMmxZn@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107634-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107634
--- Comment #6 from Eric Botcazou <ebotcazou at gcc dot gnu.org> ---
> One of the biggest drawbacks of not having one file is when you need to add
> a new section, you have to add a new file/directory rather than edditing one
> file.
Right, that's clearly not manageable. GNAT went through the same transition a
couple of years ago and ada/doc now contains 45 files, which is already quite a
bit but nowhere near the 700 now present in doc/.
next prev parent reply other threads:[~2022-11-12 8:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-11 13:27 [Bug other/107634] New: " dmalcolm at gcc dot gnu.org
2022-11-11 13:36 ` [Bug other/107634] " rguenth at gcc dot gnu.org
2022-11-11 15:49 ` pinskia at gcc dot gnu.org
2022-11-11 16:57 ` ebotcazou at gcc dot gnu.org
2022-11-11 16:58 ` ebotcazou at gcc dot gnu.org
2022-11-11 23:49 ` pinskia at gcc dot gnu.org
2022-11-11 23:53 ` pinskia at gcc dot gnu.org
2022-11-12 8:11 ` ebotcazou at gcc dot gnu.org [this message]
2022-11-13 18:17 ` marxin at gcc dot gnu.org
2022-11-13 18:30 ` marxin at gcc dot gnu.org
2022-11-13 18:33 ` pinskia at gcc dot gnu.org
2022-11-14 7:11 ` ebotcazou at gcc dot gnu.org
2022-11-14 8:44 ` 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-107634-4-3bXBZMmxZn@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).