diff mbox series

htdocs/git.html: correct spelling and use git in example

Message ID 5a5c0c9c-728c-4427-8adc-620599a60a50@jguk.org
State Unresolved
Headers
Series htdocs/git.html: correct spelling and use git in example |

Checks

Context Check Description
snail/gcc-patch-check warning Git am fail log

Commit Message

Jonny Grant Nov. 30, 2023, 5:59 p.m. UTC 
  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(-)

Comments

Joseph Myers Nov. 30, 2023, 11:56 p.m. UTC | #1 
On Thu, 30 Nov 2023, Jonny Grant wrote:

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

git:// (unencrypted / unauthenticated) is pretty widely considered 
obsolescent, I'm not sure adding a use of it (as opposed to changing any 
existing examples to use a secure connection mechanism) is a good idea.
Jonny Grant Dec. 1, 2023, 11:51 a.m. UTC | #2 
On 30/11/2023 23:56, Joseph Myers wrote:
> On Thu, 30 Nov 2023, Jonny Grant wrote:
> 
>> ChangeLog:
>>
>> 	htdocs/git.html: change example to use git:// and correct
>> 			spelling repostiory -> repository .
> 
> git:// (unencrypted / unauthenticated) is pretty widely considered 
> obsolescent, I'm not sure adding a use of it (as opposed to changing any 
> existing examples to use a secure connection mechanism) is a good idea.
> 

Hi Joseph

Thank you for your review.

Good point. I changed the ssh::// example because it doesn't work with anonymous access.
How about changing both to https:// ?

Otherwise, could the spelling correction change be applied, or is it better I submit a new patch with only that?

Kind regards
Jonny
Joseph Myers Dec. 4, 2023, 8:37 p.m. UTC | #3 
On Fri, 1 Dec 2023, Jonny Grant wrote:

> 
> 
> On 30/11/2023 23:56, Joseph Myers wrote:
> > On Thu, 30 Nov 2023, Jonny Grant wrote:
> > 
> >> ChangeLog:
> >>
> >> 	htdocs/git.html: change example to use git:// and correct
> >> 			spelling repostiory -> repository .
> > 
> > git:// (unencrypted / unauthenticated) is pretty widely considered 
> > obsolescent, I'm not sure adding a use of it (as opposed to changing any 
> > existing examples to use a secure connection mechanism) is a good idea.
> > 
> 
> Hi Joseph
> 
> Thank you for your review.
> 
> Good point. I changed the ssh::// example because it doesn't work with anonymous access.
> How about changing both to https:// ?

Using https:// makes sense for examples for anonymous access, yes.
Jonny Grant Dec. 6, 2023, 10:30 p.m. UTC | #4 
On 04/12/2023 20:37, Joseph Myers wrote:
> On Fri, 1 Dec 2023, Jonny Grant wrote:
> 
>>
>>
>> On 30/11/2023 23:56, Joseph Myers wrote:
>>> On Thu, 30 Nov 2023, Jonny Grant wrote:
>>>
>>>> ChangeLog:
>>>>
>>>> 	htdocs/git.html: change example to use git:// and correct
>>>> 			spelling repostiory -> repository .
>>>
>>> git:// (unencrypted / unauthenticated) is pretty widely considered 
>>> obsolescent, I'm not sure adding a use of it (as opposed to changing any 
>>> existing examples to use a secure connection mechanism) is a good idea.
>>>
>>
>> Hi Joseph
>>
>> Thank you for your review.
>>
>> Good point. I changed the ssh::// example because it doesn't work with anonymous access.
>> How about changing both to https:// ?
> 
> Using https:// makes sense for examples for anonymous access, yes.
> 

Okay, I'll email a revised patch in a moment with that changed.
With kind regards, Jonny
diff mbox series

Patch

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>