public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit 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: Wed, 24 Apr 2024 16:31:53 +0000 [thread overview] Message-ID: <bug-114738-4-LTDiOXsfZ9@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 #7 from GCC Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Jakub Jelinek <jakub@gcc.gnu.org>: https://gcc.gnu.org/g:97a54c05b8e338e673e1f7fb72c0e23abb571c60 commit r14-10109-g97a54c05b8e338e673e1f7fb72c0e23abb571c60 Author: Jakub Jelinek <jakub@redhat.com> Date: Wed Apr 24 18:29:12 2024 +0200 v2: DOCUMENTATION_ROOT_URL vs. release branches [PR114738] This patch moves the documentation root URL infix for release branches from get_option_url/make_doc_url to configure, such that only the default changes and when users specify a custom documentation root URL, they don't have to add gcc-MAJOR.MINOR.0 subdirectories for release branches. Tested by checking ../configure --disable-bootstrap --enable-languages=c --disable-multilib built trunk on void foo (int x) { __builtin_printf ("%ld\n", x); } testcase and looking for the URL in there, then repeating that after changing gcc/BASE-VER to 14.1.0 and again after changing it to 14.1.1, plus normal bootstrap/regtest. 2024-04-24 Jakub Jelinek <jakub@redhat.com> PR other/114738 * opts.cc (get_option_url): Revert 2024-04-17 changes. * gcc-urlifier.cc: Don't include diagnostic-core.h. (gcc_urlifier::make_doc_url): Revert 2024-04-17 changes. * configure.ac (documentation-root-url): On release branches append gcc-MAJOR.MINOR.0/ to the default DOCUMENTATION_ROOT_URL. * doc/install.texi (--with-documentation-root-url=): Document the change of the default. * configure: Regenerate.
next prev parent reply other threads:[~2024-04-24 16:31 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 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 [this message] 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-LTDiOXsfZ9@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).