public inbox for gcc-cvs-wwwdocs@sourceware.org
help / color / mirror / Atom feed
From: Richard Sandiford <rsandifo@sourceware.org>
To: gcc-cvs-wwwdocs@gcc.gnu.org
Subject: gcc-wwwdocs branch master updated. 6338f36a89e4b1d3e73f986bc8e505bc3c67fbb0
Date: Tue, 30 Jun 2020 15:05:27 +0000 (GMT)	[thread overview]
Message-ID: <20200630150527.E22303861960@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  6338f36a89e4b1d3e73f986bc8e505bc3c67fbb0 (commit)
      from  1528c44593180742ab827f9ea66d31e75b803de0 (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 6338f36a89e4b1d3e73f986bc8e505bc3c67fbb0
Author: Hu Jiangping <hujiangping@cn.fujitsu.com>
Date:   Tue Jun 30 09:13:36 2020 +0800

    Fix a typo in contribute.html

diff --git a/htdocs/contribute.html b/htdocs/contribute.html
index 80a4470e..a913565b 100644
--- a/htdocs/contribute.html
+++ b/htdocs/contribute.html
@@ -133,7 +133,7 @@ other changes applied.</p>
 <p>Documentation changes do not require a new bootstrap (a working
 bootstrap is necessary to get the build environment correct), but you
 must perform <code>make info</code> and <code>make dvi</code> and correct
-and errors.  You should investigate complaints about overfull or
+any errors.  You should investigate complaints about overfull or
 underfull hboxes from <code>make dvi</code>, as these can be the only
 indication of serious markup problems, but do not feel obliged to
 eliminate them all.</p>

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

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


hooks/post-receive
-- 
gcc-wwwdocs


                 reply	other threads:[~2020-06-30 15:05 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=20200630150527.E22303861960@sourceware.org \
    --to=rsandifo@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).