On Sun, 12 Jan 2020, Andi Kleen wrote:
> By popular demand, I did some updates to the git documentation how
> to use --reference to save disk space.
>
> Also recommend https instead of http (even though both are currently
> broken)
Thank you, Andi. Why https over http in this case? Isn't git itself
cryptographically secured? To avoid man in the middle injections via
an "alternate" repository presented?
Below is a minor update on top of yours that I applied. Hope that's
fine.
Gerald
- Log -----------------------------------------------------------------
commit 8a488efcc0f4265505205aef285ae4a7537ff390
Author: Gerald Pfeifer <ger...@pfeifer.com>
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:</p>
<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>When doing multiple clones to different repositories you can avoid
v-redownloading the whole repository by using --reference.
-For example
+<p>When doing multiple clones to several local repositories you can avoid
+re-downloading everything by using <code>--reference</code>, e.g.
+
<blockquote><code>git clone --reference original-gcc
ssh://gcc.gnu.org/git.gcc.git new-gcc</code></blockquote>
-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.</p>
+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 <code>--depth</code> 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.)</p>
<!-- Comment out till savannah gets back to us (see above)
<p>In case of problems with the repository at savannah.gnu.org please
