Re: [PATCH 01/16] bisect: write about `bisect next` in documentation

From: Junio C Hamano <gitster@pobox.com>
Date: Feb 28, 2016, 18:28 UTC
Message-ID: <xmqqbn70g048.fsf@gitster.mtv.corp.google.com>
In-Reply-To: <56D1FB53.2020404@gmx.net>

Stephan Beyer <s-beyer@gmx.net> writes:

Show 7 quoted lines

> However, it probably should be documented what "git bisect next" does
> after you've specified bad and good commits.
>
> For that, I'd like to have an extra informational paragraph.
> What about: "In general, the command computes the next commit for the
> bisection and checks it out."
> This would be neutral, in the meaning that no use case is involved.

Good thinking. Thanks for being careful; I often pretend to take an extreme position to invite a well-thought-out rebuttal, and I really like it when people respond with a good counter-proposal.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.