How to bisect the 1.6.x series of commits

Ken Thomases ken at
Thu Jan 2 13:07:05 CST 2014

On Jan 2, 2014, at 1:01 PM, Alan W. Irwin wrote:

> I have bisected Wine regressions several times in the last year
> following the cookbook in
> Those bisections were for the principal branch (or whatever you call
> it) of development. How do you do similar bisections for the branch of
> development from 1.6 to 1.6.1?  I need the name of that branch of
> development and how you specify it to the bisect process.  Sorry for
> the git newbie question, but following the above cookbook has been
> essentially my only git experience to date.
> The reason I am asking about bisecting from 1.6 to 1.6.1 is I have
> recently found some fairly strong evidence that there is an important
> regression in behavior between 1.6-rc4 and 1.6.1.

You can simply do "git bisect good wine-1.6-rc4" and "git bisect bad wine-1.6.1" or the equivalent.  Git will traverse the commits between them.  It doesn't need a branch name or anything like that.


More information about the wine-devel mailing list