public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/114738] [14 Regression] Default DOCUMENTATION_ROOT_URL vs. release branches
Date: Tue, 16 Apr 2024 10:55:07 +0000 [thread overview]
Message-ID: <bug-114738-4-g97dUwt0x0@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-114738-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114738
--- Comment #3 from Richard Biener <rguenth at gcc dot gnu.org> ---
We could also make changing it part of branching.html and have additional
directories without minor/patchlevel version, thus
https://gcc.gnu.org/onlinedocs/gcc-14/ where we could autogenerate docs in more
often (but then
14.1.0 may point to stale info when gcc-14/ is updated from the branch).
Similar issues exist of course for older snapshot builds of trunk. Not sure
if this is all well thought through given the somewhat unstable URIs we
produce. The handling of changes.html references is much more sensible.
next prev parent reply other threads:[~2024-04-16 10:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-16 9:20 [Bug other/114738] New: " jakub at gcc dot gnu.org
2024-04-16 9:20 ` [Bug other/114738] " jakub at gcc dot gnu.org
2024-04-16 10:52 ` rguenth at gcc dot gnu.org
2024-04-16 10:55 ` rguenth at gcc dot gnu.org [this message]
2024-04-16 16:41 ` pinskia at gcc dot gnu.org
2024-04-17 14:18 ` cvs-commit at gcc dot gnu.org
2024-04-18 15:10 ` jakub at gcc dot gnu.org
2024-04-24 16:31 ` cvs-commit at gcc dot gnu.org
2024-04-25 8:51 ` jakub 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-114738-4-g97dUwt0x0@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).