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. 0d66c0f73e9c54536070346bd4d52f61132ba012
Date: Mon,  5 Sep 2022 12:30:29 +0000 (GMT)	[thread overview]
Message-ID: <20220905123029.B94E33856DC0@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  0d66c0f73e9c54536070346bd4d52f61132ba012 (commit)
      from  75259d0c0541b0ffa496cb4debd7f5f545e3c055 (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 0d66c0f73e9c54536070346bd4d52f61132ba012
Author: Gerald Pfeifer <gerald@pfeifer.com>
Date:   Mon Sep 5 20:28:57 2022 +0800

    gcc-13: Remove extraneous </li> under Caveats
    
    This snuck in via 79ecba7b which added two </li>s instead of one.

diff --git a/htdocs/gcc-13/changes.html b/htdocs/gcc-13/changes.html
index 3d3d012c..5b336e04 100644
--- a/htdocs/gcc-13/changes.html
+++ b/htdocs/gcc-13/changes.html
@@ -35,7 +35,6 @@ a work-in-progress.</p>
       <code>-gstabs</code> and <code>-gxcoff</code> options) has been removed.
       (This means the <strong>dbx</strong> debugger is no longer
       supported, either.)</li>
-</li>
 </ul>
 
 

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

Summary of changes:
 htdocs/gcc-13/changes.html | 1 -
 1 file changed, 1 deletion(-)


hooks/post-receive
-- 
gcc-wwwdocs

                 reply	other threads:[~2022-09-05 12:30 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=20220905123029.B94E33856DC0@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).