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

>I would say "for the current bisection", i.e. 
> 
>$ git bisect start 
>$ git bisect terms foo bar # Scope starts here 
>... 
>The first 'bar' commit is deadbeef. # Scope ends here 
> 
>$ git bisect terms foo bar 
>You need to start by "git bisect start" 
>Do you want me to do it for you [Y/n]? 

I personnaly don't like this autostart. In the first version of this patch 
7/7 'git bisect terms' has to be called before the start. I think it is 
better because we can then use 'git bisect start rev1 rev2 ...' 

>> The next 'bisect start rev1 rev2' would be in bad/good mode. But this 
>> have to be discuted, do the user have to type 'git bisect terms' each 
>> bisection if he wants to use special terms ? 
> 
>To me, yes. If we allow arbitrary terms, then they will most likely be 
>specific to one bisect session (e.g. if I bisect "present/absent" once, 
>it tells me nothing about what I'll want for my next bisection). 

Ok. 

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]