public inbox for gcc-cvs-wwwdocs@sourceware.org
help / color / mirror / Atom feed
From: Gerald Pfeifer <gerald@sourceware.org>
To: gcc-cvs-wwwdocs@gcc.gnu.org
Subject: gcc-wwwdocs branch master updated. e1795876c8a0c7bd3136cb92c3a33df97002c711
Date: Sat, 25 May 2024 08:16:32 +0000 (GMT)	[thread overview]
Message-ID: <20240525081632.A937C385E827@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  e1795876c8a0c7bd3136cb92c3a33df97002c711 (commit)
      from  77993a3798b638d2518dcb11ac939b581ea3cea8 (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 e1795876c8a0c7bd3136cb92c3a33df97002c711
Author: Gerald Pfeifer <gerald@pfeifer.com>
Date:   Sat May 25 10:14:58 2024 +0200

    git: Fix typo

diff --git a/htdocs/git.html b/htdocs/git.html
index 22c0eec1..a6e88566 100644
--- a/htdocs/git.html
+++ b/htdocs/git.html
@@ -236,7 +236,7 @@ additional branches can also be fetched if necessary.</p>
 </ul>
 
 <p>You can download any of the additional branches by adding a suitable
-fetch specification to your local copy of the git repostiory.  For
+fetch specification to your local copy of the git repository.  For
 example, if your remote is called 'origin' (the default with git
 clone) you can add the 'dead' development branches by running:</p>
 

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

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


hooks/post-receive
-- 
gcc-wwwdocs

                 reply	other threads:[~2024-05-25  8:16 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=20240525081632.A937C385E827@sourceware.org \
    --to=gerald@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).