public inbox for gcc-cvs-wwwdocs@sourceware.org
help / color / mirror / Atom feed
From: ktkachov@gcc.gnu.org
To: gcc-cvs-wwwdocs@gcc.gnu.org
Subject: gcc-wwwdocs branch master updated. 5d68cfd83703cb8b8b0b25abb8fa91b6d44c81ee
Date: Wed, 16 Oct 2019 12:54:00 -0000	[thread overview]
Message-ID: <20191016125440.60071.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  5d68cfd83703cb8b8b0b25abb8fa91b6d44c81ee (commit)
      from  9f5f3bceb34bcb1f2cdb8f4d9a9edba06e2c6bcc (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 5d68cfd83703cb8b8b0b25abb8fa91b6d44c81ee
Author: Kyrylo Tkachov <kyrylo.tkachov@arm.com>
Date:   Wed Oct 9 16:15:00 2019 +0100

    [gcccmission.html] Replace cvs with version control

diff --git a/htdocs/gccmission.html b/htdocs/gccmission.html
index 25aa3ad..8d4b575 100644
--- a/htdocs/gccmission.html
+++ b/htdocs/gccmission.html
@@ -60,7 +60,7 @@ GCC.</p>
      as long as they accept the groundrules.</li>
  </ul></li>
 <li>Open mailing lists.</li>
-<li>Developer friendly tools and procedures (i.e., cvs, multiple
+<li>Developer friendly tools and procedures (i.e. [version control], multiple
     maintainers, etc).</li>
 <li>Conflicts of interest exist for many GCC developers; the
     developers as well as the <a href="steering.html">GCC Steering

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

Summary of changes:
 htdocs/gccmission.html |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)


hooks/post-receive
-- 
gcc-wwwdocs


                 reply	other threads:[~2019-10-16 12:54 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=20191016125440.60071.qmail@sourceware.org \
    --to=ktkachov@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).