How to bisect the 1.6.x series of commits

André Hentschel nerv at
Thu Jan 2 13:07:59 CST 2014

Am 02.01.2014 20:01, schrieb Alan W. Irwin:
> 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. I have used Wine
> 1.6-rc4 with a lot of success as a test platform for MinGW/MSYS PLplot
> builds and tests, but when I recently tried 1.6.1, my usual parallel
> tests of PLplot software failed with an error indicating plot devices
> (small dll's) cannot be dynamically loaded by the PLplot principal
> library for that version of Wine.  (The problem disappears if I do the
> tests sequentially for 1.6.1, but I obviously want to avoid that
> method of testing because it doubles the test time for my two-cpu PC.)

git checkout origin/stable
git branch stable
git checkout stable

now you can move between branches with git checkout
you can see them with git branch

More information about the wine-devel mailing list