From: "Martin Ågren" <martin.agren@gmail.com>
To: git@vger.kernel.org
Cc: Junio C Hamano <gitster@pobox.com>,
Alejandro Barreto <alejandro.barreto@ni.com>
Subject: [PATCH 0/2] documentation fixes for 2.48.0
Date: Fri, 3 Jan 2025 12:33:29 +0100 [thread overview]
Message-ID: <cover.1735903029.git.martin.agren@gmail.com> (raw)
These two patches fix some misrenderings of the built documentation,
introduced during the 2.48 cycle. As usual, the exact current behaviors
(symptoms) differ a bit between AsciiDoc and Asciidoctor.
Martin
Martin Ågren (2):
git.txt: fix heading line of tildes
gitcli.txt: typeset pathnames as monospace
Documentation/git.txt | 2 +-
Documentation/gitcli.txt | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
--
2.48.0.rc1.241.g6c04ab211c
next reply other threads:[~2025-01-03 11:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-03 11:33 Martin Ågren [this message]
2025-01-03 11:33 ` [PATCH 1/2] git.txt: fix heading line of tildes Martin Ågren
2025-01-03 11:33 ` [PATCH 2/2] gitcli.txt: typeset pathnames as monospace Martin Ågren
2025-01-03 11:39 ` [PATCH 0/2] documentation fixes for 2.48.0 Eric Sunshine
2025-01-03 11:59 ` Martin Ågren
2025-01-03 16:21 ` Junio C Hamano
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=cover.1735903029.git.martin.agren@gmail.com \
--to=martin.agren@gmail.com \
--cc=alejandro.barreto@ni.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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 NNTP newsgroup(s).