regression, troubles with setup git tree

[jpka]

Hi!
I probably found regression in Wine.
The problem is i don't know last stable release name (tag, version number) of Wine which don't have this regression.
I carefully read about regressions here http://wiki.winehq.org/RegressionTesting
Here i see a way to setup git tree somewhere between stable versions. It can be useful if i exactly know two adjacent (neighbour) stable version numbers (in article example it is git bisect good wine-0.9.36, git bisect bad wine-0.9.37). But I don't know it and want to find last working version. So I want to set up git tree to exactly known stable versions. But this wiki article don't show a way to do this. Is this way exist? Thanks!

[vitamin]

So I want to set up git tree to exactly known stable versions.

The most portable way (but dangerous if you have any source modifications, as you will loose them) is:

Code: Select all

git reset --hard wine-1.2.3

Where "wine-1.2.3" is a tag, or a commit id.

[fcmartins]

The problem is i don't know last stable release name (tag, version number) of Wine which don't have this regression.

Is there an appdb page for your application? If so, maybe there is there a working version of wine for your starting point. What I do is start with that version or, otherwise, with an old version, say 1.1.30 and if it works I do essentially a binary search compiling wine versions in between.

[jpka]

git reset --hard

Thanks, it's works and very useful!
Now, how i, after some 'git bisect's, can i see where is set git tree currently precisely? I study many git manuals but found nothing so only way i have is compile current git and run 'wine --version'. Is there more faster way / git command exist?
Also can I switch my git tree precisely one step forward and backward?
Thanks!

[vitamin]

Now, how i, after some 'git bisect's, can i see where is set git tree currently precisely?

Code: Select all

git bisect visualize