From: Jakub Jelinek <jakub@redhat.com>
To: Jonathan Wakely <jwakely@redhat.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [wwwdocs] Add anchor for contrib/gcc-git-customization.sh docs
Date: Wed, 28 Feb 2024 12:20:32 +0100 [thread overview]
Message-ID: <Zd8XAK96CDnRVQrK@tucnak> (raw)
In-Reply-To: <20240228111534.159336-1-jwakely@redhat.com>
On Wed, Feb 28, 2024 at 11:15:10AM +0000, Jonathan Wakely wrote:
> I'd like to be able to link directly to this part of the page from other
> docs.
>
> OK for wwwdocs?
LGTM.
> diff --git a/htdocs/gitwrite.html b/htdocs/gitwrite.html
> index c89cdb8f..54f8005a 100644
> --- a/htdocs/gitwrite.html
> +++ b/htdocs/gitwrite.html
> @@ -374,7 +374,7 @@ collaborators pull from there.
>
> <p>Scripts exist in the contrib directory to help manage these spaces.</p>
>
> -<h3>contrib/gcc-git-customization.sh</h3>
> +<h3 id="customization">contrib/gcc-git-customization.sh</h3>
>
> <p>This script will help set up your personal area. It will also define
> some aliases that might be useful when developing GCC. The script will
> --
> 2.43.0
Jakub
prev parent reply other threads:[~2024-02-28 11:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-28 11:15 Jonathan Wakely
2024-02-28 11:20 ` Jakub Jelinek [this message]
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=Zd8XAK96CDnRVQrK@tucnak \
--to=jakub@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jwakely@redhat.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).