This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "gcc-wwwdocs".
The branch, master has been updated
via 4e6bda6d11e75efef01135d94eda08fed967db6e (commit)
from 39c2a4c9275e9e66338ef4db4dbc2c5a4a81ab91 (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
commit 4e6bda6d11e75efef01135d94eda08fed967db6e
Author: Gerald Pfeifer <[email protected]>
Date: Sun Aug 31 22:42:27 2025 +0200
git: Prefer https:// over git://
git:// is a legacy protocol that lacks authentication and encryption.
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.
-----------------------------------------------------------------------
Summary of changes:
htdocs/git.html | 7 ++-----
1 file changed, 2 insertions(+), 5 deletions(-)
hooks/post-receive
--
gcc-wwwdocs
