public inbox for gcc-cvs-wwwdocs@sourceware.org
help / color / mirror / Atom feed
From: Martin Liska <marxin@sourceware.org>
To: gcc-cvs-wwwdocs@gcc.gnu.org
Subject: gcc-wwwdocs branch master updated. f99e457c14cdd68eca8c66b7806cb24aed5dc245
Date: Wed,  9 Nov 2022 18:39:56 +0000 (GMT)	[thread overview]
Message-ID: <20221109183956.698F33858C62@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  f99e457c14cdd68eca8c66b7806cb24aed5dc245 (commit)
      from  be113c1029ada7ea77012635a5ff531f9673a704 (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 f99e457c14cdd68eca8c66b7806cb24aed5dc245
Author: Martin Liska <mliska@suse.cz>
Date:   Wed Nov 9 19:39:08 2022 +0100

    Include docs-sources in onlinedocs.

diff --git a/htdocs/onlinedocs/index.html b/htdocs/onlinedocs/index.html
index cfa8bf5a..3410f731 100644
--- a/htdocs/onlinedocs/index.html
+++ b/htdocs/onlinedocs/index.html
@@ -1610,6 +1610,7 @@ existing release.</p>
       (<a href="https://gcc.gnu.org/onlinedocs/libgccjit.pdf">also in PDF</a>)
     </li>
     <li><a href="https://gcc.gnu.org/onlinedocs/libstdc++/">libstdc++-v3</a></li>
+    <li><a href="https://gcc.gnu.org/onlinedocs/docs-sources.tar.gz">Sphinx sources of all the manuals</a></li>
   </ul></li>
 
   <li>Internals Documentation

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

Summary of changes:
 htdocs/onlinedocs/index.html | 1 +
 1 file changed, 1 insertion(+)


hooks/post-receive
-- 
gcc-wwwdocs

                 reply	other threads:[~2022-11-09 18:39 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=20221109183956.698F33858C62@sourceware.org \
    --to=marxin@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).