mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: "Theodore Tso" <tytso@mit.edu>
Cc: "Steven Rostedt" <rostedt@goodmis.org>,
	git@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
	"Jonas Rebmann" <kernel@schlaraffenlan.de>,
	"Ricardo B. Marlière (SUSE)" <ricardo@marliere.net>
Subject: Re: FYI, git output messages are being used by other tooling
Date: Wed, 21 Oct 2026 10:19:38 -0700	[thread overview]
Message-ID: <xmqqse1zotsl.fsf@gitster.g> (raw)
In-Reply-To: <ate61iEAj4HDIvzY@mit.edu> (Theodore Tso's message of "Tue, 20 Oct 2026 15:09:20 -0400")

"Theodore Tso" <tytso@mit.edu> writes:

> 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.

  reply	other threads:[~2026-10-21 17:19 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-20 18:10 Steven Rostedt
2026-10-20 18:37 ` Junio C Hamano
2026-10-20 18:52   ` Steven Rostedt
2026-10-20 19:09   ` Theodore Tso
2026-10-21 17:19     ` Junio C Hamano [this message]
2026-10-21 18:26     ` Andreas Schwab
2026-10-20 19:23   ` Steven Rostedt
2026-10-20 19:28     ` Kristoffer Haugsbakk
2026-10-20 19:33       ` Steven Rostedt
2026-10-20 22:48       ` Theodore Tso
2026-10-21 17:53         ` Kristoffer Haugsbakk
2026-10-20 18:44 ` Kristoffer Haugsbakk

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=xmqqse1zotsl.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=kernel@schlaraffenlan.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ricardo@marliere.net \
    --cc=rostedt@goodmis.org \
    --cc=tytso@mit.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®