public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Hans-Peter Nilsson <hp@bitrange.com>
To: David Malcolm <dmalcolm@redhat.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH 2/9] wwwdocs: gcc-14: add URLs to some options
Date: Sun, 7 Apr 2024 15:32:13 -0400 (EDT)	[thread overview]
Message-ID: <alpine.BSF.2.20.16.2404071528070.54221@arjuna.pair.com> (raw)
In-Reply-To: <20240404164208.2437213-3-dmalcolm@redhat.com>

On Thu, 4 Apr 2024, David Malcolm wrote:

> Signed-off-by: David Malcolm <dmalcolm@redhat.com>
> ---
>  htdocs/gcc-14/changes.html | 23 ++++++++++++++++-------
>  1 file changed, 16 insertions(+), 7 deletions(-)
> 
> diff --git a/htdocs/gcc-14/changes.html b/htdocs/gcc-14/changes.html
> index 5cc729c5..397458d5 100644
> --- a/htdocs/gcc-14/changes.html
> +++ b/htdocs/gcc-14/changes.html
> @@ -149,26 +149,33 @@ a work-in-progress.</p>
>      to enable additional hardening.
>    </li>
>    <li>
> -    New option <code>-fhardened</code>, an umbrella option that enables a set
> -    of hardening flags.  The options it enables can be displayed using the
> +    New option
> +    <a href="https://gcc.gnu.org/onlinedocs/gcc/Instrumentation-Options.html#index-fhardened"><code>-fhardened</code></a>,

Shouldn't those URLs better point to a specific version, lest 
they might break with any newer release?

The question is "a bit" rhetorical, since there appears to be 
nothing at onlinedocs/gcc-14.0.0/ (and "nearby numbers").

Still, maybe there ought to be a copy of onlinedocs/gcc/ that is 
frozen at time of release.

brgds, H-P

  reply	other threads:[~2024-04-07 19:32 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-04 16:41 [pushed] wwwdocs: gcc-14: various changes David Malcolm
2024-04-04 16:42 ` [PATCH 1/9] wwwdocs: gcc-14: add caveat about not using analyzer on C++ David Malcolm
2024-04-04 16:42 ` [PATCH 2/9] wwwdocs: gcc-14: add URLs to some options David Malcolm
2024-04-07 19:32   ` Hans-Peter Nilsson [this message]
2024-04-04 16:42 ` [PATCH 3/9] wwwdocs: gcc-14: add null_terminated_string_arg attribute David Malcolm
2024-04-04 16:42 ` [PATCH 4/9] wwwdocs: gcc-14: c++: note changes to source quoting in template errors David Malcolm
2024-04-04 16:42 ` [PATCH 5/9] wwwdocs: gcc-14: libgccjit changes David Malcolm
2024-04-04 16:42 ` [PATCH 6/9] wwwdocs: gcc-14: improvements to automatic doc URLs for options David Malcolm
2024-04-04 16:42 ` [PATCH 7/9] wwwdocs: gcc-14: improvements for plugin authors David Malcolm
2024-04-04 16:42 ` [PATCH 8/9] wwwdocs: gcc-14: analyzer improvements David Malcolm
2024-04-04 16:42 ` [PATCH 9/9] wwwdocs: gcc-14: add 'Improvements to SARIF support' section David Malcolm

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=alpine.BSF.2.20.16.2404071528070.54221@arjuna.pair.com \
    --to=hp@bitrange.com \
    --cc=dmalcolm@redhat.com \
    --cc=gcc-patches@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).