From: Mike Frysinger <vapier@gentoo.org>
To: gdb-patches@sourceware.org
Subject: [PATCH htdocs] use <h3> under <h2>
Date: Tue, 12 Dec 2023 18:16:24 -0500 [thread overview]
Message-ID: <20231212231624.22569-1-vapier@gentoo.org> (raw)
We use <h1> for the site's title, <h2> for the page title, and <h3>
for sections under that. These two pages were using <h2> for page
sections lower down, so fix them up.
---
committee/index.html | 2 +-
mailing-lists/index.html | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/committee/index.html b/committee/index.html
index bcf51df2e3ac..710344a2d7c6 100644
--- a/committee/index.html
+++ b/committee/index.html
@@ -61,7 +61,7 @@ not be generally involved in day-to-day development.
The GDB Maintainers also appoint the <a href="release-manager.html">GDB
Release Manager</a>.
-<h2>Appointed Maintainers</h2>
+<h3>Appointed Maintainers</h3>
<p>
The current official FSF-appointed GDB Maintainers are listed below,
diff --git a/mailing-lists/index.html b/mailing-lists/index.html
index 892bc72999f2..a14ff93f044f 100644
--- a/mailing-lists/index.html
+++ b/mailing-lists/index.html
@@ -115,7 +115,7 @@ name for historical reasons</dd>
</dt> <dd> A read-only list for <tt>cron</tt> log
messages and other dull boring stuff.</dd>
-<h2>Former Resources, No Longer Active Nor Monitored</h2>
+<h3>Former Resources, No Longer Active Nor Monitored</h3>
<dt><a href="news:gnu.gdb.bug"> <b>gnu.gdb.bug</b></a></dt>
<dd> (mail relay <a href="https://lists.gnu.org/archive/html/bug-gdb/"
--
2.43.0
next reply other threads:[~2023-12-12 23:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-12 23:16 Mike Frysinger [this message]
2023-12-15 15:50 ` Tom Tromey
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=20231212231624.22569-1-vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=gdb-patches@sourceware.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).