ChangeLog:

        htdocs/git.html: change example to use git:// and correct
                        spelling repostiory -> repository .



>From fad03a107f5f8734e9eeafb618cdb30fa100cbbb Mon Sep 17 00:00:00 2001
From: Jonathan Grant <j...@jguk.org>
Date: Thu, 30 Nov 2023 17:55:49 +0000
Subject: [PATCH] htdocs/git.html: change example to use git:// and correct
 spelling repostiory -> repository

---
 htdocs/git.html | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/htdocs/git.html b/htdocs/git.html
index 22c0eec1..45d5cf9d 100644
--- a/htdocs/git.html
+++ b/htdocs/git.html
@@ -44,7 +44,7 @@ through, you can replace <code>git://</code> with 
<code>https://</code>.
 <p>If there is another local repository accessible you can avoid
 re-downloading everything by using <code>--reference</code>, e.g.</p>
 
-<blockquote><code>git clone --reference original-gcc --dissociate 
ssh://gcc.gnu.org/git/gcc.git new-gcc</code></blockquote>
+<blockquote><code>git clone --reference original-gcc --dissociate 
git://gcc.gnu.org/git/gcc.git new-gcc</code></blockquote>
 
 <p>But if you own this other copy, you probably want to use
 separate <a href="#worktrees">worktrees</a> instead of multiple clones.
@@ -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>
 
-- 
2.40.1

Reply via email to