From: Todd Zullinger <tmz@pobox.com>
To: "Jean-Noël Avila" <jn.avila@free.fr>
Cc: git@vger.kernel.org
Subject: [PATCH 0/3] doc lint fixes for pack-refs and refs
Date: Sat, 12 Sep 2026 15:14:59 -0400 [thread overview]
Message-ID: <20260912191509.844954-1-tmz@pobox.com> (raw)
I was reading git-refs(1) after noticing it learned some new tricks in the
2.56.0 release notes. The formatting stood out because the first two commands,
migrate and verify are bold (in the man pages) but subsequent commands are not.
The HTML is similarly affected, with those commands colored differently than
the rest in our online documentation:
https://git-scm.com/docs/git-refs
This is due to inconsistent backtick-quotes.
This led me to the lint check, which I think might benefit from the small
change here to match commands as well as options. Running something like this
reports a number of files which could also use some tweaks:
cd Documentation && for i in *.adoc; do
output=$(perl lint-documentation-style.perl <$i 2>&1)
[[ -n $output ]] && printf '\n%s:\n%s\n' $i "$output"
done
I _think_ we want to backtick-quote those when using the synopsis style. (If
not, then the change is wrong and we should remove the backticks from the two
commands in git-refs.adoc and other places.)
As git-refs.adoc includes pack-refs-options.adoc, I updated it to consistently
use backtick quoting and converted the only other file which includes it,
git-pack-refs.adoc.
Todd Zullinger (3):
doc lint: match commands as well as options for synopsis style check
doc/pack-refs: convert synopsis and options to new style
doc/refs: backtick-quote commands and options consistently
Documentation/git-pack-refs.adoc | 8 ++++----
Documentation/git-refs.adoc | 14 +++++++-------
Documentation/lint-documentation-style.perl | 4 ++--
Documentation/pack-refs-options.adoc | 10 +++++-----
4 files changed, 18 insertions(+), 18 deletions(-)
--
2.56.0.rc0
next reply other threads:[~2026-09-12 19:15 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-12 19:14 Todd Zullinger [this message]
2026-09-12 19:15 ` [PATCH 1/3] doc lint: match commands as well as options for synopsis style check Todd Zullinger
2026-09-12 19:15 ` [PATCH 2/3] doc/pack-refs: convert synopsis and options to new style Todd Zullinger
2026-09-12 19:15 ` [PATCH 3/3] doc/refs: backtick-quote commands and options consistently Todd Zullinger
2026-09-13 10:26 ` [PATCH 0/3] doc lint fixes for pack-refs and refs Jean-Noël AVILA
2026-09-13 14:14 ` Todd Zullinger
2026-09-14 12:46 ` [PATCH v2 0/2] " Todd Zullinger
2026-09-14 12:46 ` [PATCH v2 1/2] doc/pack-refs: convert synopsis and options to new style Todd Zullinger
2026-09-14 15:30 ` Junio C Hamano
2026-09-14 15:43 ` Todd Zullinger
2026-09-15 13:15 ` Todd Zullinger
2026-09-14 12:46 ` [PATCH v2 2/2] doc/refs: backtick-quote commands and options consistently Todd Zullinger
2026-09-15 13:10 ` [PATCH v2 0/2] doc lint fixes for pack-refs and refs Todd Zullinger
2026-09-15 16:25 ` Junio C Hamano
2026-09-15 13:10 ` [PATCH v3 1/2] doc/pack-refs: convert synopsis and options to new style Todd Zullinger
2026-09-15 13:10 ` [PATCH v3 2/2] doc/refs: backtick-quote commands and options consistently Todd Zullinger
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=20260912191509.844954-1-tmz@pobox.com \
--to=tmz@pobox.com \
--cc=git@vger.kernel.org \
--cc=jn.avila@free.fr \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.