From: Junio C Hamano <gitster@pobox.com>
To: "Kristoffer Haugsbakk" <code@khaugsbakk.name>
Cc: "Matthieu Moy" <git@matthieu-moy.fr>, git@vger.kernel.org
Subject: Re: [PATCH 1/2] bisect: document "terms" subcommand more fully
Date: Thu, 08 Feb 2024 08:48:08 -0800 [thread overview]
Message-ID: <xmqqil2yq4vr.fsf@gitster.g> (raw)
In-Reply-To: <a8e67945-153b-43bb-b1b0-ea24fa786097@app.fastmail.com> (Kristoffer Haugsbakk's message of "Thu, 08 Feb 2024 07:36:55 +0100")
"Kristoffer Haugsbakk" <code@khaugsbakk.name> writes:
> On Wed, Feb 7, 2024, at 22:44, Junio C Hamano wrote:
>> The documentation for "git bisect terms", although it did not hide
>> any information, was a bit incomplete and forced readers to fill in
>> the blanks to get the complete picture.
>>
>> Acked-by: Matthieu Moy <git@matthieu-moy.fr>
>> Signed-off-by: Junio C Hamano <gitster@pobox.com>
>> ---
>
> Past tense? How about:
>
> The documentation for "git bisect terms"---although it does not hide
> any information---is a bit incomplete and forces readers to fill in
> the blanks to get the complete picture.
Right.
Thanks.
next prev parent reply other threads:[~2024-02-08 16:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-09 11:58 [BUG] git-bisect man page description of terms command doesn't mention old/new support Britton Kerin
2023-12-09 16:13 ` Re* " Junio C Hamano
2023-12-11 12:34 ` Matthieu Moy
2023-12-11 15:05 ` Junio C Hamano
2024-02-07 21:44 ` [PATCH 0/2] minute "git bisect" doc updates Junio C Hamano
2024-02-07 21:44 ` [PATCH 1/2] bisect: document "terms" subcommand more fully Junio C Hamano
2024-02-08 6:36 ` Kristoffer Haugsbakk
2024-02-08 16:48 ` Junio C Hamano [this message]
2024-02-07 21:44 ` [PATCH 2/2] bisect: document command line arguments for "bisect start" Junio C Hamano
2024-02-08 16:18 ` Jean-Noël Avila
2024-02-09 9:39 ` [PATCH 0/2] minute "git bisect" doc updates Christian Couder
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=xmqqil2yq4vr.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=code@khaugsbakk.name \
--cc=git@matthieu-moy.fr \
--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 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.