public inbox for gcc-cvs-wwwdocs@sourceware.org
help / color / mirror / Atom feed
From: Gerald Pfeifer <gerald@sourceware.org>
To: gcc-cvs-wwwdocs@gcc.gnu.org
Subject: gcc-wwwdocs branch master updated. e46e9f37331b3b1c1971d6f8984a41a55a919da3
Date: Tue, 7 Jul 2020 20:55:13 +0000 (GMT) [thread overview]
Message-ID: <20200707205513.65FDD3858D35@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 e46e9f37331b3b1c1971d6f8984a41a55a919da3 (commit)
from 0485c980009c2d2533cd34734a4918f4523d0cfe (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 e46e9f37331b3b1c1971d6f8984a41a55a919da3
Author: Gerald Pfeifer <gerald@pfeifer.com>
Date: Tue Jul 7 22:54:50 2020 +0200
Switch www.doxygen.nl to https.
diff --git a/htdocs/codingconventions.html b/htdocs/codingconventions.html
index a08ddcbb..c0377315 100644
--- a/htdocs/codingconventions.html
+++ b/htdocs/codingconventions.html
@@ -752,7 +752,7 @@ outside the build system are discouraged, and should be sent upstream
first. </li>
<li>libstdc++-v3: In docs/doxygen, comments in *.cfg.in are
-partially autogenerated from <a href="http://www.doxygen.nl">the
+partially autogenerated from <a href="https://www.doxygen.nl">the
Doxygen tool</a>. In docs/html, the ext/lwg-* files are copied from <a
href="http://www.open-std.org/jtc1/sc22/wg21/">the C++ committee homepage</a>,
the 27_io/binary_iostream_* files are copies of Usenet postings, and most
-----------------------------------------------------------------------
Summary of changes:
htdocs/codingconventions.html | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
hooks/post-receive
--
gcc-wwwdocs
reply other threads:[~2020-07-07 20:55 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=20200707205513.65FDD3858D35@sourceware.org \
--to=gerald@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).