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

On Tue, May 19, 2015 at 10:31 AM, Stefan Beller [off-list ref] wrote:

$ git bisect bad
383c3427afa3201eb05e931825c5c2f20616b58b is the first bad commit
commit 383c3427afa3201eb05e931825c5c2f20616b58b
Author: Eric Sunshine [off-list ref]
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 [off-list ref]
    Signed-off-by: Junio C Hamano [off-list ref]

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?