public inbox for gcc-cvs-wwwdocs@sourceware.org
help / color / mirror / Atom feed
From: Jonathan Wakely <redi@sourceware.org>
To: gcc-cvs-wwwdocs@gcc.gnu.org
Subject: gcc-wwwdocs branch master updated. 7bf5cf1e11dfff357a85c54dd5d9d56abbd26653
Date: Fri,  1 Mar 2024 15:35:28 +0000 (GMT)	[thread overview]
Message-ID: <20240301153528.BB0E03858416@sourceware.org> (raw)

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "gcc-wwwdocs".

The branch, master has been updated
       via  7bf5cf1e11dfff357a85c54dd5d9d56abbd26653 (commit)
      from  df2bc49fc018c2b1aeb27030fe1967470d0d4ec3 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
commit 7bf5cf1e11dfff357a85c54dd5d9d56abbd26653
Author: Jonathan Wakely <jwakely@redhat.com>
Date:   Wed Feb 28 11:14:41 2024 +0000

    Add anchor for contrib/gcc-git-customization.sh docs

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

-----------------------------------------------------------------------

Summary of changes:
 htdocs/gitwrite.html | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)


hooks/post-receive
-- 
gcc-wwwdocs

                 reply	other threads:[~2024-03-01 15:35 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20240301153528.BB0E03858416@sourceware.org \
    --to=redi@sourceware.org \
    --cc=gcc-cvs-wwwdocs@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).