From: Junio C Hamano <gitster@pobox.com>
Date: Tue, 12 May 2015 23:24:00 GMT
Subject: Re: [PATCH v2] bisect: improve output when bad commit is found
Message-ID: <xmqqwq0dcrcf.fsf@gitster.dls.corp.google.com>
In-Reply-To: <1431472751-20974-1-git-send-email-tbsaunde@tbsaunde.org>

Trevor Saunders <tbsaunde@tbsaunde.org> writes:

> When the first bad commit has been found git bisect prints something
> like this:
>
> 	<40 char sha1> is the first bad commit
> 	Commit <40 char sha1>
> 	...
>
> 	:100644 100644 10f5e57... a46cfeb... M  bisect.c
> 	:100755 100755 ae3fec2... 65a19fa... M  git-bisect.sh
>
> The raw diff output is not really useful, and its kind of silly to print
> the sha1 twice.  Instead lets print something like this:
>
> 	The first bad commit is
> 	Commit <sha1>
> 	...

According to +CCouder, this change will break existing people's use
cases.

See $gmane/268881