[PATCH v2 7/7] bisect: allows any terms set by user

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Matthieu Moy <Matthieu.Moy@xxxxxxxxxxxxxxx> writes: 

>> 
>>># terms_defined is 0 when the user did not define the terms explicitely 
>>># yet. This is the case when running 'git bisect start bad_rev good_rev' 
>>># before we see an explicit reference to a term. 
>>>terms_defined=0 
>> 
>> The thing is: 
>> 'git bisect reset 
>> git bisect new HEAD 

>"git bisect new" does not exist. Did you mean "git bisect start HEAD"? 

No I meant new but it can be 'git bisect bad' aswell
So 
'
git bisect reset
git bisect bad
answer yes to "autostart ?"
'

>I don't understand. The user didn't say either "bad" or "good", so in 
>both cases we haven't seen a term yet. Or I misunderstood what you meant 
>by "define a term". 

In the case I rewrited, we saw a 'bad' but terms_defined value in bisect_start
(called by the autostart) is 0. 


Thanks.

--
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



[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]