mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Junio C Hamano <gitster@pobox.com>
Cc: 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: Tue, 20 Oct 2026 14:52:56 -0400	[thread overview]
Message-ID: <20261020145256.411985b3@gandalf.local.home> (raw)
In-Reply-To: <xmqq8q3sw75e.fsf@gitster.g>

On Tue, 20 Oct 2026 11:37:01 -0700
Junio C Hamano <gitster@pobox.com> wrote:

> Steven Rostedt <rostedt@goodmis.org> writes:
> 
> > Hi,
> >
> > I just want to let you folks know that ktest.pl (tools/testing/ktest/ in
> > the Linux kernel repository) parses the output of git to display the first
> > bad commit found in an automated git bisect.
> >
> > The output was recently updated via: 0c0f93e7fa64 ("bisect: print bisect
> > terms in single quotes") which made ktest.pl fail to find the bad commit.
> >
> > 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 could look into changing it. The code was written in 2010 so it could
perhaps be updated ;-)

Thanks,

-- Steve

  reply	other threads:[~2026-10-20 18:53 UTC|newest]

Thread overview: 8+ 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 [this message]
2026-10-20 19:09   ` Theodore Tso
2026-10-20 19:23   ` Steven Rostedt
2026-10-20 19:28     ` Kristoffer Haugsbakk
2026-10-20 19:33       ` Steven Rostedt
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=20261020145256.411985b3@gandalf.local.home \
    --to=rostedt@goodmis.org \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=kernel@schlaraffenlan.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ricardo@marliere.net \
    /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®