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

Re: [PATCH v2] describe: limit default ref iteration to tags

From
Junio C Hamano <gitster@pobox.com>
Date
Jun 9, 2026, 13:23 UTC
Message-ID
<xmqqpl1zsv8s.fsf@gitster.g>
In-Reply-To
<20260609110957.GB1509396@coredump.intra.peff.net>
Jeff King <peff@peff.net> writes:
Show 20 quoted lines
> So while it is perhaps reasonable to document every detail in case
> somebody later wants to verify or reproduce timings, it is a little
> overwhelming when trying to tell a story, the core of which is:
>
>   In a repo with ~120k refs, ~300 of which were tags, running:
>
>     git describe --exact-match $some_tag
>
>   went from ~170ms to ~10ms, since we no longer needed to iterate all of
>   those other refs.
>
> That has _way_ less detail, but makes the point succinctly.
>
> I dunno. I am not trying to pick apart your commit in particular, but am
> more interested in the broader use of AI commit messages going forward.
> This kind of verbosity is quite common in the output (from my limited
> experience), and I think creates more work for reviewers. Should we be
> expecting contributors to make things more concise before submitting
> (either manually or through prompting)? Or do people even agree that the
> shorter version is preferable? I could be the only one.

Count me in. You are the one who often gives us a patch with 60 lines that explains a single line change, but I haven't found these 60 lines are _overly verbose_ in the same way as AI generated log messages.

Previous: Jeff KingNext: D. Ben Knoble
Message 3 of 12 in “describe: limit default ref iteration to tags”
  1. describe: limit default ref iteration to tagsTamir Duberstein, Jun 9, 2026
  2. Jeff KingJun 9, 2026
  3. Junio C HamanoJun 9, 2026
  4. D. Ben KnobleJun 9, 2026
  5. Jeff KingJun 11, 2026
  6. Tamir DubersteinJun 9, 2026
  7. Junio C HamanoJun 10, 2026
  8. Patrick SteinhardtJun 10, 2026
  9. Junio C HamanoJun 10, 2026
  10. Jeff KingJun 11, 2026
  11. describe: limit default ref iteration to tagsTamir Duberstein, Jun 10, 2026
  12. Jeff KingJun 11, 2026

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.