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

Re: FYI, git output messages are being used by other tooling

From
Theodore Tso <tytso@mit.edu>
Date
Oct 20, 2026, 19:09 UTC
Message-ID
<ate61iEAj4HDIvzY@mit.edu>
In-Reply-To
<xmqq8q3sw75e.fsf@gitster.g>
On Tue, Oct 20, 2026 at 11:37:01AM -0500, Junio C Hamano wrote:
Show 8 quoted lines
> > The change is being addressed:
> >
> >   https://lore.kernel.org/all/20261009-ktest-git-bisect-v1-1-1d1428f6cbf4@marliere.net/
> >
> > But I figured it would be good for you to know about this dependency.
> 
> Shouldn't the script instead seeing "git show bisect/bad" instead?
>

I wonder if we should have something like a "git bisect --format=json" option to facilitate programs that are running git bisect in some kind of automation. Steven's email caused me to check my test appliance[1] but fortunately the only thing I depend on is whether the otuput of "git bisect good/bad" has a string which contains "is the first bad commit" or not. If someone has a commit with the one-line summary which contains that string, or if git ever changed the git bisect text output, or someone tried to set LANG to Chinese or some such, hilarity would ensue. :-)

[1] https://github.com/tytso/xfstests-bld/blob/master/test-appliance/files/usr/local/lib/gce-server/util/git/git.go

A structured output that contained the result of the "git bisect good|bad", and the first bad commit if it has been found, would be certainly be a more reliable way for automated git bisection harneses to rely upon. It'd be great if that was something that was in git 3.0.

						- Ted
Previous: Steven RostedtNext: Junio C Hamano
Message 4 of 12 in “FYI, git output messages are being used by other tooling”
  1. Steven RostedtOct 20, 2026
  2. Junio C HamanoOct 20, 2026
  3. Steven RostedtOct 20, 2026
  4. Theodore TsoOct 20, 2026
  5. Junio C HamanoOct 21, 2026
  6. Andreas SchwabOct 21, 2026
  7. Steven RostedtOct 20, 2026
  8. Kristoffer HaugsbakkOct 20, 2026
  9. Steven RostedtOct 20, 2026
  10. Theodore TsoOct 20, 2026
  11. Kristoffer HaugsbakkOct 21, 2026
  12. Kristoffer HaugsbakkOct 20, 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.