public inbox for git@vger.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Michael Lyons <git@michael.lyo.nz>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 1/1] doc: git-bisect: convert to new doc format
Date: Sun, 11 Jan 2026 19:13:39 -0800	[thread overview]
Message-ID: <xmqq1pjvplp8.fsf@gitster.g> (raw)
In-Reply-To: <20260111204316.836446-2-git@michael.lyo.nz> (Michael Lyons's message of "Sun, 11 Jan 2026 15:42:48 -0500")

Michael Lyons <git@michael.lyo.nz> writes:

> - Change placeholders to glossary terms

I see you changed <rev> to <commit> and I guess the point above is a
reference to that change, but I cannot be sure if (1) there are
things other than <rev> that you changed for the same reason, and
(2) if "glossary has it" is the reason for the change (we have
"revision" in there, and it is widely known that "rev" is an
abbreviation for it in the context of these documentation pages).

You can rephrase the above, perhaps like

    Some parameters are described with placeholders with less common
    words, which is unnecessarily harder to understand by new
    readers.  Use <commit> instead of <rev>.

to avoid the problem, if <rev> -> <commit> is the only change for
this reason.  If there are more words you addressed, perhaps you can
replace the last sentence.


> - Refer to placeholders in prose
> - Delimit runnable commands and CLI args with backticks
> - Link internal heading

The same comments may apply to these three.

Thanks.

  reply	other threads:[~2026-01-12  3:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-11 20:42 [PATCH 0/1] doc: git-bisect to synopsis Michael Lyons
2026-01-11 20:42 ` [PATCH 1/1] doc: git-bisect: convert to new doc format Michael Lyons
2026-01-12  3:13   ` Junio C Hamano [this message]
2026-01-12 21:23   ` Jean-Noël AVILA
2026-01-13 12:54     ` Junio C Hamano
2026-01-13 18:45       ` Jean-Noël Avila

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=xmqq1pjvplp8.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=git@michael.lyo.nz \
    --cc=git@vger.kernel.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