public inbox for gcc-cvs-wwwdocs@sourceware.org help / color / mirror / Atom feed
From: jsm28@gcc.gnu.org To: gcc-cvs-wwwdocs@gcc.gnu.org Subject: gcc-wwwdocs branch master updated. c4df04644677895890df1c0dc24c6f3c157f90a8 Date: Tue, 14 Jan 2020 23:37:00 -0000 [thread overview] Message-ID: <20200114233709.44760.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 c4df04644677895890df1c0dc24c6f3c157f90a8 (commit) from 3af4155933a9d3b8506b56c16865879b098ab4cf (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 c4df04644677895890df1c0dc24c6f3c157f90a8 Author: Joseph Myers <joseph@codesourcery.com> Date: Tue Jan 14 23:36:33 2020 +0000 Correct git config command syntax. There is no --set option, git config sets variables without such an option. diff --git a/htdocs/gitwrite.html b/htdocs/gitwrite.html index 85a0da2..f420fe2 100644 --- a/htdocs/gitwrite.html +++ b/htdocs/gitwrite.html @@ -78,7 +78,7 @@ git clone git+ssh://<i>username</i>@gcc.gnu.org/git/gcc.git gcc using <code>git config</code>:</p> <blockquote><p><code> -git config --set remote.origin.url git+ssh://<i>username</i>@gcc.gnu.org/git/gcc.git +git config remote.origin.url git+ssh://<i>username</i>@gcc.gnu.org/git/gcc.git </code></p></blockquote> <p>To avoid the nuisance of having to supply your passphrase for each ----------------------------------------------------------------------- Summary of changes: htdocs/gitwrite.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) hooks/post-receive -- gcc-wwwdocs
reply other threads:[~2020-01-14 23:37 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=20200114233709.44760.qmail@sourceware.org \ --to=jsm28@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).