From: Mike Frysinger <vapier@gentoo.org>
To: gdb-patches@sourceware.org
Subject: [PATCH htdocs] current: use <code> for file paths
Date: Tue, 12 Dec 2023 18:22:44 -0500 [thread overview]
Message-ID: <20231212232244.24437-1-vapier@gentoo.org> (raw)
Not sure if we do this elsewhere, but rendering file paths in monospace
text is fairly common in practice (e.g. GNU manuals). There doesn't
seem to be other usage in this repo, nor GNU guidance in general (as
that only exists for texi sources), so just use <code>.
---
current/index.html | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/current/index.html b/current/index.html
index db78d46f9075..4467b87bf4a0 100644
--- a/current/index.html
+++ b/current/index.html
@@ -76,7 +76,7 @@ git clone https://sourceware.org/git/binutils-gdb.git
If you already have a read-only copy of git on hand then there is no
need to re-check out a source tree. Instead, you can edit your
-.git/config to change the remote to use the read-write URL.
+<code>.git/config</code> to change the remote to use the read-write URL.
For example, you might have:
--
2.43.0
next reply other threads:[~2023-12-12 23:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-12 23:22 Mike Frysinger [this message]
2023-12-15 15:53 ` 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=20231212232244.24437-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).