public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Joseph Myers <joseph@codesourcery.com>
To: <gcc-patches@gcc.gnu.org>
Subject: Re: Replace update_web_docs_svn with update_web_docs_git
Date: Mon, 13 Jan 2020 18:43:00 -0000	[thread overview]
Message-ID: <alpine.DEB.2.21.2001131816080.11452@digraph.polyomino.org.uk> (raw)
In-Reply-To: <alpine.DEB.2.21.2001131746190.11452@digraph.polyomino.org.uk>

I've also applied this corresponding web page update.

diff --git a/htdocs/releasing.html b/htdocs/releasing.html
index 5d08550c..48853f9c 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

-- 
Joseph S. Myers
joseph@codesourcery.com

  reply	other threads:[~2020-01-13 18:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-13 18:11 Joseph Myers
2020-01-13 18:43 ` Joseph Myers [this message]
2020-01-13 21:53 ` Jonathan Wakely
2020-01-13 22:10   ` Joseph Myers
2020-01-13 23:26     ` Jonathan Wakely

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=alpine.DEB.2.21.2001131816080.11452@digraph.polyomino.org.uk \
    --to=joseph@codesourcery.com \
    --cc=gcc-patches@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).