public inbox for gcc-cvs-wwwdocs@sourceware.org
help / color / mirror / Atom feed
From: segher@gcc.gnu.org
To: gcc-cvs-wwwdocs@gcc.gnu.org
Subject: gcc-wwwdocs branch master updated. 26f4802d2ffd7aa182e559414638b6c546054f64
Date: Tue, 04 Feb 2020 20:09:00 -0000	[thread overview]
Message-ID: <20200204200951.70599.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  26f4802d2ffd7aa182e559414638b6c546054f64 (commit)
      from  2a7b0ec3a0bed79a098da0f797923c052dedfcf0 (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 26f4802d2ffd7aa182e559414638b6c546054f64
Author: Segher Boessenkool <segher@kernel.crashing.org>
Date:   Tue Feb 4 20:09:34 2020 +0000

    git: Fix typo in url

diff --git a/htdocs/git.html b/htdocs/git.html
index 66d68eb..7fd22a9 100644
--- a/htdocs/git.html
+++ b/htdocs/git.html
@@ -44,7 +44,7 @@ through, you can replace <code>git://</code> with <code>https://</code>.
 <p>If there is another local repository accessible you can avoid
 re-downloading everything by using <code>--reference</code>, e.g.</p>
 
-<blockquote><code>git clone --reference original-gcc --dissociate ssh://gcc.gnu.org/git.gcc.git new-gcc</code></blockquote>
+<blockquote><code>git clone --reference original-gcc --dissociate ssh://gcc.gnu.org/git/gcc.git new-gcc</code></blockquote>
 
 <p>But if you own this other copy, you probably want to use
 separate <a href="#worktrees">worktrees</a> instead of multiple clones.

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

Summary of changes:
 htdocs/git.html | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)


hooks/post-receive
-- 
gcc-wwwdocs


                 reply	other threads:[~2020-02-04 20:09 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=20200204200951.70599.qmail@sourceware.org \
    --to=segher@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: link
Be 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).