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. a5241468f3bb551ba33fd97fb2869a41636d6dc8
Date: Mon, 13 Jan 2020 18:12:00 -0000	[thread overview]
Message-ID: <20200113181235.10529.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  a5241468f3bb551ba33fd97fb2869a41636d6dc8 (commit)
      from  22f8a6f0286575c467575ce76879e26ff8d7e8f6 (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 a5241468f3bb551ba33fd97fb2869a41636d6dc8
Author: Joseph Myers <joseph@codesourcery.com>
Date:   Mon Jan 13 18:12:05 2020 +0000

    Update releasing documentation to refer to update_web_docs_git.

diff --git a/htdocs/releasing.html b/htdocs/releasing.html
index 5d08550..48853f9 100644
--- a/htdocs/releasing.html
+++ b/htdocs/releasing.html
@@ -89,9 +89,9 @@ the main web page, and add a proper news item there as well.</li>
 and add a link from the main <code>buildstat.html</code> page.</li>
 
 <li>Generate online documentation for the new release with
-<code>update_web_docs_svn</code>.  The appropriate command to run (as gccadmin)
-to generate the documentation would be <code>scripts/update_web_docs_svn
--rgcc_3_0_2_release -dgcc-3.0.2</code> (with the current version
+<code>update_web_docs_git</code>.  The appropriate command to run (as gccadmin)
+to generate the documentation would be <code>scripts/update_web_docs_git
+-r3.0.2 -dgcc-3.0.2</code> (with the current version
 number inserted).  Link to it from <code>onlinedocs/index.html</code>
 (but don't break URLs to documentation for previous releases even if
 you remove the links to it).  Create additionally

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

Summary of changes:
 htdocs/releasing.html | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)


hooks/post-receive
-- 
gcc-wwwdocs


                 reply	other threads:[~2020-01-13 18:12 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=20200113181235.10529.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).