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.