From: Eli Zaretskii <eliz@gnu.org>
To: Tom Tromey <tromey@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Use lower-case in @sc in the documentation
Date: Thu, 18 May 2023 21:34:55 +0300 [thread overview]
Message-ID: <838rdlv67k.fsf@gnu.org> (raw)
In-Reply-To: <20230518182049.3144025-1-tromey@adacore.com> (message from Tom Tromey via Gdb-patches on Thu, 18 May 2023 12:20:49 -0600)
> Cc: Tom Tromey <tromey@adacore.com>
> Date: Thu, 18 May 2023 12:20:49 -0600
> From: Tom Tromey via Gdb-patches <gdb-patches@sourceware.org>
>
> Eli pointed out that @sc only produces small caps for lower case
> letters in its argument, so it's weird to write it using upper-case
> letters. This patch fixes the instances I found.
> ---
> gdb/doc/gdb.texinfo | 4 ++--
> gdb/doc/python.texi | 34 +++++++++++++++++-----------------
> 2 files changed, 19 insertions(+), 19 deletions(-)
Thanks, this falls under the "obvious fix" rules.
Approved-By: Eli Zaretskii <eliz@gnu.org>
prev parent reply other threads:[~2023-05-18 18:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-18 18:20 Tom Tromey
2023-05-18 18:34 ` Eli Zaretskii [this message]
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=838rdlv67k.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=tromey@adacore.com \
/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).