public inbox for gcc-cvs-wwwdocs@sourceware.org
help / color / mirror / Atom feed
From: Eric Gallager <egallager@sourceware.org>
To: gcc-cvs-wwwdocs@gcc.gnu.org
Subject: gcc-wwwdocs branch master updated. 060631da2a638ad72d68f7e955b799f659465f40
Date: Mon, 11 Oct 2021 20:30:24 +0000 (GMT)	[thread overview]
Message-ID: <20211011203024.D13B23858D35@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  060631da2a638ad72d68f7e955b799f659465f40 (commit)
      from  2e760df142212a340c3954197606a6606da4ca65 (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 060631da2a638ad72d68f7e955b799f659465f40
Author: Eric Gallager <egall@gwmail.gwu.edu>
Date:   Mon Oct 11 16:30:01 2021 -0400

    Fix minor typo in command for git customization

diff --git a/htdocs/gitwrite.html b/htdocs/gitwrite.html
index 51f611f0..6afd1778 100644
--- a/htdocs/gitwrite.html
+++ b/htdocs/gitwrite.html
@@ -505,7 +505,7 @@ check the branch out locally.  You can do that afterwards with
 <h3>contrib/git-add-user-branch.sh</h3>
 
 <p>before this script can be used, your personal space access should be
-  set up by running <code>contrib/gcc-git-cusomization.sh</code>.</p>
+  set up by running <code>contrib/gcc-git-customization.sh</code>.</p>
 
 <p>The script takes two arguments, the name of the new branch to create
   and a <i>ref</i> to create it from.  The personal prefix for the new

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

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


hooks/post-receive
-- 
gcc-wwwdocs


                 reply	other threads:[~2021-10-11 20:30 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=20211011203024.D13B23858D35@sourceware.org \
    --to=egallager@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).