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. 97a5a775c87bbb702af5224800e9b10a3e74817e
Date: Sat, 28 Jan 2023 01:23:11 +0000 (GMT)	[thread overview]
Message-ID: <20230128012311.B8B4A3858D20@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  97a5a775c87bbb702af5224800e9b10a3e74817e (commit)
      from  ea33f839826fdb4135a2ad97ead6f94a3f01aa78 (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 97a5a775c87bbb702af5224800e9b10a3e74817e
Author: Gerald Pfeifer <gerald@pfeifer.com>
Date:   Sat Jan 28 02:21:27 2023 +0100

    codingconventions: Replace <tt> markup by <code>

diff --git a/htdocs/codingconventions.html b/htdocs/codingconventions.html
index 7e2a092d..8b3cb8bb 100644
--- a/htdocs/codingconventions.html
+++ b/htdocs/codingconventions.html
@@ -756,7 +756,7 @@ first. </li>
 
 <li>libstdc++-v3:  The doc/doxygen/user.cfg.in file is partially autogenerated
 from <a href="https://www.doxygen.nl">the Doxygen tool</a> (and regenerated
-using <tt>doxygen -u</tt>).
+using <code>doxygen -u</code>).
 The files in doc/html are generated from the Docbook sources in doc/xml
 and should not be changed manually.
 The files in doc/xml/gnu are based on the GNU licenses and should not

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

Summary of changes:
 htdocs/codingconventions.html | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)


hooks/post-receive
-- 
gcc-wwwdocs

                 reply	other threads:[~2023-01-28  1:23 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=20230128012311.B8B4A3858D20@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).