From: Jeff King <peff@peff.net>
To: Christian Couder <christian.couder@gmail.com>
Cc: Junio C Hamano <gitster@pobox.com>,
Trevor Saunders <tbsaunde@tbsaunde.org>,
git <git@vger.kernel.org>
Subject: Re: [PATCH v2] bisect: improve output when bad commit is found
Date: Wed, 13 May 2015 17:42:29 -0400 [thread overview]
Message-ID: <20150513214228.GA17350@peff.net> (raw)
In-Reply-To: <CAP8UFD14LuyaVcoNHxR00ZeGgHWXbuW_QdVf4YqZWzgMdufUjQ@mail.gmail.com>
On Wed, May 13, 2015 at 11:39:41AM +0200, Christian Couder wrote:
> > 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
next prev parent reply other threads:[~2015-05-13 21:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-12 23:19 [PATCH v2] bisect: improve output when bad commit is found Trevor Saunders
2015-05-12 23:24 ` Junio C Hamano
2015-05-13 0:54 ` Trevor Saunders
2015-05-13 1:13 ` Junio C Hamano
2015-05-13 1:36 ` Jeff King
2015-05-13 5:48 ` Junio C Hamano
2015-05-13 9:39 ` Christian Couder
2015-05-13 21:42 ` Jeff King [this message]
2015-05-13 9:10 ` Christian Couder
2015-05-13 17:25 ` Trevor Saunders
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=20150513214228.GA17350@peff.net \
--to=peff@peff.net \
--cc=christian.couder@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=tbsaunde@tbsaunde.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.