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

Re: [PATCH] rev-parse: don't trim bisect refnames

From
Michael Haggerty <mhagger@alum.mit.edu>
Date
Sep 6, 2017, 15:09 UTC
Message-ID
<CAMy9T_FQHei2XgidRqcBPabKCGq2g282KgYDhe-e9XqSjJE1gw@mail.gmail.com>
In-Reply-To
<20170906115310.kxgjrnmrehm5m32q@sigill.intra.peff.net>
On Wed, Sep 6, 2017 at 1:53 PM, Jeff King <peff@peff.net> wrote:
Show 13 quoted lines
> [...]
> Subject: [PATCH] rev-parse: don't trim bisect refnames
>
> Using for_each_ref_in() with a full refname has always been
> a questionable practice, but it became an error with
> b9c8e7f2fb (prefix_ref_iterator: don't trim too much,
> 2017-05-22), making "git rev-parse --bisect" pretty reliably
> show a BUG.
>
> Commit 03df567fbf (for_each_bisect_ref(): don't trim
> refnames, 2017-06-18) fixed this case for revision.c, but
> rev-parse handles this option on its own. We can use the
> same solution here (and piggy-back on its test).
It looks good to me.
Michael
Previous: Jeff KingNext: Linus Torvalds
Message 7 of 9 in “BUG: attempt to trim too many characters”
  1. Linus TorvaldsSep 5, 2017
  2. Jeff KingSep 5, 2017
  3. Linus TorvaldsSep 5, 2017
  4. Jeff KingSep 5, 2017
  5. Linus TorvaldsSep 5, 2017
  6. rev-parse: don't trim bisect refnamesJeff King, Sep 6, 2017
  7. Michael HaggertySep 6, 2017
  8. Linus TorvaldsSep 13, 2017
  9. Jeff KingSep 13, 2017

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.