git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH] bisect: revise manpage

From
Christian Couder <christian.couder@gmail.com>
Date
Jun 26, 2015, 12:44 UTC
Message-ID
<CAP8UFD1GwH1ewapraL6cms04OVk8wHdtv+TJ7=HKL0_CLGjK-g@mail.gmail.com>
In-Reply-To
<12a2e2d5e545459837b5eb2356cfc2fe4e3ef631.1435317576.git.mhagger@alum.mit.edu>
On Fri, Jun 26, 2015 at 1:30 PM, Michael Haggerty <mhagger@alum.mit.edu> wrote:
[...]
> +Eventually there will be no more revisions left to bisect, and the
> +command will print out a description of the first bad commit, and also
> +create a reference called `refs/bisect/bad` that points at that
> +commit.

This could be understood as meaning that `refs/bisect/bad` is created only at the end of the bisection.

> -Eventually there will be no more revisions left to bisect, and you
> -will have been left with the first bad kernel revision in "refs/bisect/bad".
The original looks better to me in this regard.

Thanks, Christian.

Previous: Michael HaggertyNext: Matthieu Moy
Message 2 of 13 in “bisect: revise manpage”
  1. bisect: revise manpageMichael Haggerty, Jun 26, 2015
  2. Christian CouderJun 26, 2015
  3. Matthieu MoyJun 26, 2015
  4. Christian CouderJun 26, 2015
  5. Michael HaggertyJun 26, 2015
  6. Christian CouderJun 26, 2015
  7. Matthieu MoyJun 26, 2015
  8. Junio C HamanoJun 26, 2015
  9. 3/7 Documentation/bisect: revise overall contentMatthieu Moy, Jun 26, 2015
  10. Matthieu MoyJun 26, 2015
  11. Michael HaggertyJun 26, 2015
  12. Matthieu MoyJun 26, 2015
  13. Junio C HamanoJun 26, 2015

Read the whole thread, see it on lore, or plain text.

$ 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.