From mboxrd@z Thu Jan 1 00:00:00 1970
Return-Path:
Received: (qmail 28591 invoked by alias); 12 Jan 2020 20:47:27 -0000
Mailing-List: contact gcc-cvs-wwwdocs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id:
List-Archive:
List-Post:
List-Help:
Sender: gcc-cvs-wwwdocs-owner@gcc.gnu.org
Received: (qmail 28535 invoked by uid 9022); 12 Jan 2020 20:47:27 -0000
Date: Sun, 12 Jan 2020 20:47:00 -0000
Message-ID: <20200112204727.28532.qmail@sourceware.org>
From: gerald@gcc.gnu.org
To: gcc-cvs-wwwdocs@gcc.gnu.org
Subject: gcc-wwwdocs branch master updated. 8a488efcc0f4265505205aef285ae4a7537ff390
X-Git-Refname: refs/heads/master
X-Git-Reftype: branch
X-Git-Oldrev: 6dea84381d9a60d776e3f377d2c7a499396904ce
X-Git-Newrev: 8a488efcc0f4265505205aef285ae4a7537ff390
X-SW-Source: 2020/txt/msg00012.txt
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 8a488efcc0f4265505205aef285ae4a7537ff390 (commit)
from 6dea84381d9a60d776e3f377d2c7a499396904ce (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 8a488efcc0f4265505205aef285ae4a7537ff390
Author: Gerald Pfeifer
Date: Sun Jan 12 21:43:59 2020 +0100
Refine the note on local clones, add markup, break a long line.
diff --git a/htdocs/git.html b/htdocs/git.html
index 41e2d953..7f40c0f6 100644
--- a/htdocs/git.html
+++ b/htdocs/git.html
@@ -45,17 +45,18 @@ check out the GCC sources using the following command:
If you are behind a firewall that does not allow the git protocol
through, you can replace git://
with https://
.
-
When doing multiple clones to different repositories you can avoid
-redownloading the whole repository by using --reference.
-For example
+
When doing multiple clones to several local repositories you can avoid
+re-downloading everything by using --reference
, e.g.
+
git clone --reference original-gcc ssh://gcc.gnu.org/git.gcc.git new-gcc
-This will also save some disk space. Git will do this automatically when cloning from a local repository on the same file system. It is also possible to do a
-shallow checkout with --depth to limit history, but that might limit your
-ability to work with existing branches.
-You should only use the https protocol if
-the git protocol does not work; the https protocol has a higher server
-overhead associated with it and will be slower.
+This will also save disk space. Git will do this automatically when cloning
+from a local repository on the same file system. It is also possible to do a
+shallow checkout with --depth
to limit history, but that might
+limit your ability to work with existing branches.
+
+(Only use the https protocol if the git protocol does not work; https has
+a higher server overhead and will be slower.)