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

Re: [PATCH v2] bisect: improve output when bad commit is found

From
Jeff King <peff@peff.net>
Date
May 13, 2015, 21:42 UTC
Message-ID
<20150513214228.GA17350@peff.net>
In-Reply-To
<CAP8UFD14LuyaVcoNHxR00ZeGgHWXbuW_QdVf4YqZWzgMdufUjQ@mail.gmail.com>
On Wed, May 13, 2015 at 11:39:41AM +0200, Christian Couder wrote:
Show 10 quoted lines
> > It is not clear to me that people are actually scripting around the
> > output. Between the exit code and the stable output in BISECT_LOG, that
> > seems like a much more preferable way for scripted uses to find out what
> > happened.
> >
> > Of course, that is not a guarantee that nobody scraped stderr, but at
> > least it makes me feel better that they're Doing It Wrong. :)
> 
> Aren't we sending the "XXXX is the first bad commit" and the diff-tree
> to stdout?

Good point. I'm much more sympathetic to people scraping stdout than stderr. I do still think we would do better to direct them to more robust formats, though.

-Peff
Previous: Christian CouderNext: Christian Couder
Message 8 of 10 in “bisect: improve output when bad commit is found”
  1. bisect: improve output when bad commit is foundTrevor Saunders, May 12, 2015
  2. Junio C HamanoMay 12, 2015
  3. Trevor SaundersMay 13, 2015
  4. Junio C HamanoMay 13, 2015
  5. Jeff KingMay 13, 2015
  6. Junio C HamanoMay 13, 2015
  7. Christian CouderMay 13, 2015
  8. Jeff KingMay 13, 2015
  9. Christian CouderMay 13, 2015
  10. Trevor SaundersMay 13, 2015

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.