Re: [PATCH] htdocs/git.html: correct spelling and use git in example
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
Re: [PATCH] htdocs/git.html: correct spelling and use git in example
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. -- Joseph S. Myers jos...@codesourcery.com
Re: [PATCH] htdocs/git.html: correct spelling and use git in example
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
Re: [PATCH] htdocs/git.html: correct spelling and use git in example
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. -- Joseph S. Myers jos...@codesourcery.com
[PATCH] htdocs/git.html: correct spelling and use git in example
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 Date: Thu, 30 Nov 2023 17:55:49 + 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 git:// with https://. If there is another local repository accessible you can avoid re-downloading everything by using --reference, e.g. -git clone --reference original-gcc --dissociate ssh://gcc.gnu.org/git/gcc.git new-gcc +git clone --reference original-gcc --dissociate git://gcc.gnu.org/git/gcc.git new-gcc But if you own this other copy, you probably want to use separate worktrees instead of multiple clones. @@ -236,7 +236,7 @@ additional branches can also be fetched if necessary. 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: -- 2.40.1
