From: Stephan Beyer Date: Fri, 26 Feb 2016 21:38:40 GMT Subject: Re: [PATCH 02/16] bisect: add test for the bisect algorithm Message-ID: <56D0C5E0.2020703@gmx.net> In-Reply-To: Hi Christian, On 02/26/2016 07:53 AM, Christian Couder wrote: >> +test_expect_success 'bisect algorithm works in linear history with an odd number of commits' ' >> + git bisect start A7 && >> + git bisect next && >> + test "$(git rev-parse HEAD)" = "$(git rev-parse A3)" \ >> + -o "$(git rev-parse HEAD)" = "$(git rev-parse A4)" > > I thought that we should not use "-o" and "-a" but instead "|| test" > and "&& test". Why is this? I understand the && instead of -a thing (test atomicity), however, for || this results in an ugly + git bisect next && + ( test "$(git rev-parse HEAD)" = "$(git rev-parse A3)" || + test "$(git rev-parse HEAD)" = "$(git rev-parse A4)" ) Right? (Otherwise a failure of e.g. "git bisect start A7" would run the command after || (which may still be fine in some cases but is wrong in most of the other cases). However, what do you think about this? diff --git a/t/t8010-bisect-algorithm.sh b/t/t8010-bisect-algorithm.sh index bda59da..ae50e7c 100755 --- a/t/t8010-bisect-algorithm.sh +++ b/t/t8010-bisect-algorithm.sh @@ -8,6 +8,16 @@ exec