2009/3/5 Johannes Schindelin <Johannes.Schindelin@xxxxxx>:
> Hi,
>
> On Thu, 5 Mar 2009, Junio C Hamano wrote:
>
>> [...] personally I never felt the need for "run" to work without any bad
>> one, as the first few rounds would almost always end up to be a
>> debugging session of the run script for me, as in:
>>
>> ... oh, somebody broke this somewhere ...
>> ... write a validate script ...
>> $ edit runme ; chmod +x runme
>> $ ./runme
>> ... yeah, it is broken and runme script detects breakage
>> $ git checkout HEAD~200
>> $ ./runme
>> ... ok, it used to work here and runme exits Ok
>> $ git bisect good
>> $ git bisect bad @{-1}
>> $ ./runme
>> ... ok, runme script appears to be ok
>> $ git bisect run ./runme
>
> That reminds me of a personal gripe with "bisect run": You cannot use it
> like this:
>
> $ git bisect run 'make test'
>
> as it interprets 'make test' as a name of an executable. That makes
> 'bisect run' rather less useful to me.
A very quick test seems to show that:
$ git bisect run make test
Works as you want. Maybe a quick example of this could be added to
the man page.
>
> Ciao,
> Dscho
>
>
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
