Jonny suggested this a while ago, when originally I didn't fully understand; now I do. :-)
Pushed. Gerald git:// is a legacy protocol that lacks authentication and encryption. --- htdocs/git.html | 7 ++----- 1 file changed, 2 insertions(+), 5 deletions(-) diff --git a/htdocs/git.html b/htdocs/git.html index 0b55a970..ced2048b 100644 --- a/htdocs/git.html +++ b/htdocs/git.html @@ -35,16 +35,13 @@ separate repository</a>.)</p> check out the GCC sources using the following command:</p> <blockquote><p> -<code>git clone git://gcc.gnu.org/git/gcc.git SomeLocalDir</code> +<code>git clone https://gcc.gnu.org/git/gcc.git SomeLocalDir</code> </p></blockquote> -<p>If you are behind a firewall that does not allow the git protocol -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 https://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. -- 2.50.1
