From: "Martin Liška" <mliska@suse.cz>
To: gcc-patches@gcc.gnu.org
Subject: [PATCH (pushed)] Include docs-sources in onlinedocs.
Date: Wed, 9 Nov 2022 19:39:48 +0100 [thread overview]
Message-ID: <44555a43-3840-bf91-ee39-0a468ae524be@suse.cz> (raw)
---
htdocs/onlinedocs/index.html | 1 +
1 file changed, 1 insertion(+)
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
--
2.38.0
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=44555a43-3840-bf91-ee39-0a468ae524be@suse.cz \
--to=mliska@suse.cz \
--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).