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. cb7e6cbe56b65b665e7abbedf66b271a87b39e1b
Date: Sun,  7 May 2023 08:42:21 +0000 (GMT)	[thread overview]
Message-ID: <20230507084221.E317B3858D28@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  cb7e6cbe56b65b665e7abbedf66b271a87b39e1b (commit)
      from  ce8961b192b8f29055609cbd7c2fc10d105cd340 (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 cb7e6cbe56b65b665e7abbedf66b271a87b39e1b
Author: Gerald Pfeifer <gerald@pfeifer.com>
Date:   Sun May 7 10:40:53 2023 +0200

    onlinedocs: Fix markup
    
    Commit 7c0b3155efaecf8c9bfa5192ca99acc7356bec71 for GCC 13.1 "stole" an
    opening <details open> from the existing GCC 13.2 entry.

diff --git a/htdocs/onlinedocs/index.html b/htdocs/onlinedocs/index.html
index 421d1d0b..e72f5bfa 100644
--- a/htdocs/onlinedocs/index.html
+++ b/htdocs/onlinedocs/index.html
@@ -111,6 +111,7 @@
   </ul>
 </details>
 
+<details open>
  <summary>GCC 12.2 manuals:</summary>
   <ul>
     <li><a href="https://gcc.gnu.org/onlinedocs/gcc-12.2.0/gcc/">GCC

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

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


hooks/post-receive
-- 
gcc-wwwdocs

                 reply	other threads:[~2023-05-07  8:42 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=20230507084221.E317B3858D28@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).