From: "Martin Liška" <mliska@suse.cz>
To: Richard Biener <richard.guenther@gmail.com>
Cc: gcc-patches@gcc.gnu.org, David Malcolm <dmalcolm@redhat.com>,
Gerald Pfeifer <gerald@pfeifer.com>
Subject: Re: [PATCH (pushed)] sphinx: update diagnostics URLs
Date: Wed, 9 Nov 2022 14:07:13 +0100 [thread overview]
Message-ID: <706e9523-a41f-34ff-e417-42dcfcb6fe74@suse.cz> (raw)
In-Reply-To: <CAFiYyc11gTNXuVS+j0bGJauPfrtGrx4djYktFtZUHwn59rjrRg@mail.gmail.com>
On 11/9/22 14:00, Richard Biener wrote:
> Do we need a redirect at the old location?
Well, what's not working are older gcc releases that still point to "master" branch
documentation:
gcc --version
gcc (SUSE Linux) 12.2.1 20221020 [revision 0aaef83351473e8f4eb774f8f999bbe87a4866d7]
...
https://gcc.gnu.org/onlinedocs/gcc/Warning-Options.html#index-Wunused-parameter
these should point ideally to:
https://gcc.gnu.org/onlinedocs/gcc-12.2.0/gcc/Warning-Options.html#index-Wunused-parameter
anyway, we can provider redirect for these, I'll ask Gerald.
Martin
next prev parent reply other threads:[~2022-11-09 13:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-09 12:12 Martin Liška
2022-11-09 13:00 ` Richard Biener
2022-11-09 13:07 ` Martin Liška [this message]
2022-11-09 13:15 ` Richard Biener
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=706e9523-a41f-34ff-e417-42dcfcb6fe74@suse.cz \
--to=mliska@suse.cz \
--cc=dmalcolm@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gerald@pfeifer.com \
--cc=richard.guenther@gmail.com \
/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).