Re: [PATCH] bisect: report actual bisect_state() argument on error

From: Ramkumar Ramachandra <r@artagnon.com>
Date: Jan 10, 2022, 10:04 UTC
Message-ID: <570bd7cb-ab03-41ec-9bc5-8bcc261990b9@www.fastmail.com>
In-Reply-To: <5d8c8a72-6c4f-35e4-a6a4-4ed7d6f23c4e@web.de>

René Scharfe wrote:

> This doesn't fix your problem, only replace the "(null)" in the error
> messages with the actual state name -- which may be useful for
> diagnosing its cause, though.

Thanks René! As a next step, perhaps we can also abbreviate the SHAs in the error messages?

Warm regards, Ram

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