gcc-wwwdocs branch master updated. 6e3c70f5e39e2249ddadc56f801801dd881fe66c

[gerald@gcc.gnu.org]

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  6e3c70f5e39e2249ddadc56f801801dd881fe66c (commit)
      from  d65a8b4f8d4d625070b3f8cbb07b13dfe1116ae6 (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 6e3c70f5e39e2249ddadc56f801801dd881fe66c
Author: Gerald Pfeifer <gerald@pfeifer.com>
Date:   Mon Jan 13 08:18:04 2020 +0100

    Fix markup in the new section around cloning.

diff --git a/htdocs/git.html b/htdocs/git.html
index 7f40c0f6..52051423 100644
--- a/htdocs/git.html
+++ b/htdocs/git.html
@@ -46,11 +46,11 @@ check out the GCC sources using the following command:</p>
 through, you can replace <code>git://</code> with <code>https://</code>.
 
 <p>When doing multiple clones to several local repositories you can avoid
-re-downloading everything by using <code>--reference</code>, e.g.
+re-downloading everything by using <code>--reference</code>, e.g.</p>
 
 <blockquote><code>git clone --reference original-gcc ssh://gcc.gnu.org/git.gcc.git new-gcc</code></blockquote>
 
-This will also save disk space. Git will do this automatically when cloning
+<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.

-----------------------------------------------------------------------

Summary of changes:
 htdocs/git.html | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)


hooks/post-receive
-- 
gcc-wwwdocs