public inbox for gcc-cvs-wwwdocs@sourceware.org help / color / mirror / Atom feed
From: gerald@gcc.gnu.org To: gcc-cvs-wwwdocs@gcc.gnu.org Subject: gcc-wwwdocs branch master updated. 8a488efcc0f4265505205aef285ae4a7537ff390 Date: Sun, 12 Jan 2020 20:47:00 -0000 [thread overview] Message-ID: <20200112204727.28532.qmail@sourceware.org> (raw) 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 <gerald@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 -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 ----------------------------------------------------------------------- Summary of changes: htdocs/git.html | 19 ++++++++++--------- 1 file changed, 10 insertions(+), 9 deletions(-) hooks/post-receive -- gcc-wwwdocs
reply other threads:[~2020-01-12 20:47 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20200112204727.28532.qmail@sourceware.org \ --to=gerald@gcc.gnu.org \ --cc=gcc-cvs-wwwdocs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).