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
Junio C Hamano <gitster@pobox.com>
Date
Oct 21, 2026, 17:19 UTC
Message-ID
<xmqqse1zotsl.fsf@gitster.g>
In-Reply-To
<ate61iEAj4HDIvzY@mit.edu>
"Theodore Tso" <tytso@mit.edu> writes:
Show 5 quoted lines
> 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.

I am afraid that anything we propose today would be too late for the 3.0 breaking changes list, but a new optional feature does not have to wait for 3.0 at all ;-) I do not know if the format to do so should be .jsonl or .yaml or what, but I agree that machine-readable status output would be a helpful addition for automation.

Thanks.
Previous: Theodore TsoNext: Andreas Schwab
Message 5 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.