From: Junio C Hamano <gitster@pobox.com>
To: git@vger.kernel.org
Subject: [PATCH 0/2] minute "git bisect" doc updates
Date: Wed, 7 Feb 2024 13:44:34 -0800 [thread overview]
Message-ID: <20240207214436.538586-1-gitster@pobox.com> (raw)
In-Reply-To: <24a42fa6-7bc4-4a3b-8bf4-a0ef85dc457a@matthieu-moy.fr>
"git bisect" documentation was a bit sketchy on alternative keywords
"new" and "old", that are used to signal if a command is from the
part of the history that is newer or older than "a significant
event" the bisection is trying to find. Here are two small patches
that improves the documentation.
I am trying to flush my "stalled topics" queue. Here is a small and
(hopefully) easy-to-finish one.
The original discussion was from early December 2023 and can be
found at
https://lore.kernel.org/git/CAC4O8c9ieZC4SBJf54ZuTfAvnkhGuDaibBQ-m9Zw_n5VhUFPag@mail.gmail.com/
Junio C Hamano (2):
bisect: document "terms" subcommand more fully
bisect: document command line arguments for "bisect start"
Documentation/git-bisect.txt | 10 ++++++----
1 file changed, 6 insertions(+), 4 deletions(-)
--
2.43.0-561-g235986be82
next prev parent reply other threads:[~2024-02-07 21:44 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 ` Junio C Hamano [this message]
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
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=20240207214436.538586-1-gitster@pobox.com \
--to=gitster@pobox.com \
--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