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. 29c11a61ae5e2b210cdf564ae7a49945afea2e44
Date: Tue, 14 Jan 2020 23:50:00 -0000	[thread overview]
Message-ID: <20200114235002.74101.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  29c11a61ae5e2b210cdf564ae7a49945afea2e44 (commit)
      from  4ce5c94abb8129cb0182acade6a0504d58e8799f (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 29c11a61ae5e2b210cdf564ae7a49945afea2e44
Author: Joseph Myers <joseph@codesourcery.com>
Date:   Tue Jan 14 23:48:36 2020 +0000

    Remove warning at top of git web pages.
    
    Although the documentation is still a work in progress, with various
    forms of git usage (e.g. contrib/gcc-git-customization.sh) not yet
    documented and development branches not yet listed on git.html as they
    are on svn.html, the warning about the conversion still being in
    progress is no longer accurate, so remove it.

diff --git a/htdocs/git.html b/htdocs/git.html
index 0a8294e..70cc7b7 100644
--- a/htdocs/git.html
+++ b/htdocs/git.html
@@ -16,10 +16,6 @@
 <body>
 <h1>GCC: Anonymous read-only Git access</h1>
 
-<p><strong>The conversion from SVN to Git is in progress.  The
-repository described here may not yet be the final version of that
-conversion.</strong></p>
-
 <p>Our Git source repository is available read-only to the public at
 large.  That way you can pick up any version (including releases) of
 GCC that is in our repository.</p>
diff --git a/htdocs/gitwrite.html b/htdocs/gitwrite.html
index e55cfa9..3cda6a4 100644
--- a/htdocs/gitwrite.html
+++ b/htdocs/gitwrite.html
@@ -10,10 +10,6 @@
 
 <h1>Read-write Git access</h1>
 
-<p><strong>The conversion from SVN to Git is in progress.  The
-repository described here may not yet be the final version of that
-conversion.</strong></p>
-
 <p>We have read/write access to the Git repository available for
 maintainers and significant developers.</p>
 

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

Summary of changes:
 htdocs/git.html      | 4 ----
 htdocs/gitwrite.html | 4 ----
 2 files changed, 8 deletions(-)


hooks/post-receive
-- 
gcc-wwwdocs


                 reply	other threads:[~2020-01-14 23:50 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=20200114235002.74101.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: 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).