From: Jonny Grant <jg@jguk.org>
To: gcc-patches@gcc.gnu.org
Subject: [PATCH] htdocs/git.html: correct spelling and use git in example
Date: Thu, 30 Nov 2023 17:59:56 +0000 [thread overview]
Message-ID: <5a5c0c9c-728c-4427-8adc-620599a60a50@jguk.org> (raw)
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 <jg@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
next reply other threads:[~2023-11-30 19:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-30 17:59 Jonny Grant [this message]
2023-11-30 23:56 ` Joseph Myers
2023-12-01 11:51 ` Jonny Grant
2023-12-04 20:37 ` Joseph Myers
2023-12-06 22:30 ` Jonny Grant
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=5a5c0c9c-728c-4427-8adc-620599a60a50@jguk.org \
--to=jg@jguk.org \
--cc=gcc-patches@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).