Re: test suite failure t5570, 8 with v2.4.1-168-g1ea28e1

From: Stefan Beller <sbeller@google.com>
Date: May 19, 2015, 17:34 UTC
Message-ID: <CAGZ79kbYUNjD79T+1LqgLNf=_ym-keq57FoQhby_aqn_sPFYSg@mail.gmail.com>
In-Reply-To: <CAGZ79kaNWDB2qg2-x-+2ccV1hC7Y0K8TQVPQNkjMotggwsRRzw@mail.gmail.com>

On Tue, May 19, 2015 at 10:31 AM, Stefan Beller <sbeller@google.com> wrote:

Show 15 quoted lines

> $ git bisect bad
> 383c3427afa3201eb05e931825c5c2f20616b58b is the first bad commit
> commit 383c3427afa3201eb05e931825c5c2f20616b58b
> Author: Eric Sunshine <sunshine@sunshineco.com>
> Date:   Mon May 4 03:25:14 2015 -0400
>
>     t1007: add hash-object --literally tests
>
>     git-hash-object learned a --literally option in 5ba9a93
>     (hash-object: add --literally option, 2014-09-11). Check that
>     --literally allows object creation with a bogus type, with two
>     type strings whose length is reasonably short and very long.
>
>     Signed-off-by: Eric Sunshine <sunshine@sunshineco.com>
>     Signed-off-by: Junio C Hamano <gitster@pobox.com>

When looking at the commit I don't think I found the right one. So I went back to HEAD^ (being v2.1.0-243-g0c3db67), which also tests bad now. Is there a way to force git bisect to change good to bad?