public inbox for gcc-cvs-wwwdocs@sourceware.org
help / color / mirror / Atom feed
From: Jonathan Wakely <redi@sourceware.org>
To: gcc-cvs-wwwdocs@gcc.gnu.org
Subject: gcc-wwwdocs branch master updated. 2b70f89ff4df991b32d3680f56485470ec978bc6
Date: Fri, 19 Jun 2020 15:06:13 +0000 (GMT)	[thread overview]
Message-ID: <20200619150613.692563851C0D@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  2b70f89ff4df991b32d3680f56485470ec978bc6 (commit)
      from  227fc3d39521d7552190a148bafb6d2c4092ba22 (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 2b70f89ff4df991b32d3680f56485470ec978bc6
Author: Jonathan Wakely <jwakely@redhat.com>
Date:   Fri Jun 19 16:06:05 2020 +0100

    Fix typo in docs for Git write access

diff --git a/htdocs/gitwrite.html b/htdocs/gitwrite.html
index 36bb1a20..5332e2f5 100644
--- a/htdocs/gitwrite.html
+++ b/htdocs/gitwrite.html
@@ -516,7 +516,7 @@ check the branch out locally.  You can do that afterwards with
 </pre></blockquote>
 
 <p>will set up a branch called <code>topic</code> on the server and a
-  local branch called <code>me/topic</code> that tracks it.  The banch
+  local branch called <code>me/topic</code> that tracks it.  The branch
   can then be pushed using:</p>
 
 <blockquote><pre>

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

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


hooks/post-receive
-- 
gcc-wwwdocs


                 reply	other threads:[~2020-06-19 15:06 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=20200619150613.692563851C0D@sourceware.org \
    --to=redi@sourceware.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).