From mboxrd@z Thu Jan 1 00:00:00 1970
Return-Path:
Received: (qmail 20399 invoked by alias); 12 Jan 2020 19:03:08 -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 20327 invoked by uid 9855); 12 Jan 2020 19:03:07 -0000
Date: Sun, 12 Jan 2020 19:03:00 -0000
Message-ID: <20200112190307.20324.qmail@sourceware.org>
From: ak@gcc.gnu.org
To: gcc-cvs-wwwdocs@gcc.gnu.org
Subject: gcc-wwwdocs branch master updated. 6dea84381d9a60d776e3f377d2c7a499396904ce
X-Git-Refname: refs/heads/master
X-Git-Reftype: branch
X-Git-Oldrev: 9a2b6d593f69ecca9a6a68b5d1d33d8f13a981d4
X-Git-Newrev: 6dea84381d9a60d776e3f377d2c7a499396904ce
X-SW-Source: 2020/txt/msg00011.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 6dea84381d9a60d776e3f377d2c7a499396904ce (commit)
from 9a2b6d593f69ecca9a6a68b5d1d33d8f13a981d4 (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 6dea84381d9a60d776e3f377d2c7a499396904ce
Author: Andi Kleen
Date: Sun Jan 12 11:02:42 2020 -0800
Document how to use --reference
diff --git a/htdocs/git.html b/htdocs/git.html
index 0166ff7..41e2d95 100644
--- a/htdocs/git.html
+++ b/htdocs/git.html
@@ -43,9 +43,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 http://
.
-You should only use the http protocol if
-the git protocol does not work; the http protocol has a higher server
+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
+
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.