wine users - Jul 2010 - A little doubt about bug 21659

Using wine 1.2 I have again the bug 21659, I see the status is UNCONFIRMED.

Is needed for afected users make the regression testing?.

Thanks

http://bugs.winehq.org/show_bug.cgi?id=21659

are u sure you included all needed libs while compiling wine?

Altair wrote:
> Is needed for afected users make the regression testing?.
> 
Yes.

I am surprised:

Bisecting: 10131 revisions left to test after this
[a261137593a475eb2a5d2e2169d151c06f231f76] shell32: Fix German folder names.

only this....

Altair wrote:
> I am surprised:
> 
> Bisecting: 10131 revisions left to test after this
> [a261137593a475eb2a5d2e2169d151c06f231f76] shell32: Fix German folder
names.
> 
> only this....
What did you set as git bisect good and git bisect bad? According to the bug
report, this regression happened somewhere between 1.1.36 and 1.1.38, so you
shouldn't have anywhere near that many revisions to test, not even from the
start.  When I set those two versions as good and bad, git tells me there are
373 revisions left to test.

You're not done until git tells you "[commit number] is first bad
commit."

You need to reread the instructions for regression testing.
http://wiki.winehq.org/RegressionTesting

Altair <wineforum-user at winehq.org> wrote:
>Sent: Jul 21, 2010 5:23 AM
>To: wine-users at winehq.org
>Subject: [Wine]  Re: A little doubt about bug 21659
>
>
>
>Okay, I go to try again. Is hard to me, the explanation in RegressionTesting
page are short for me.
>
>Example: I not understand how git "know" where is the 1.1.44
version and where the 1.2, ecause I use separate
>folders I think I need found any good manual in spanish about use git.
You need to find a good site, in Spanish, on how to use Git and what Git does. 
Basically, Git stores markers for each commit to the basic branch, usually
called master.  When we 'tag' a release, it creates a static image of
the branch at that point.  Using Git commands you can pick a starting
'tag' and a closing 'tag' and Git will go through the dictionary
of commits and remove all of the commits above a certaing point with the bisect
command.  This is repeated, moving forward for a 'good' bisect, moving
backwards for a bad.  This is repeated until no more commits are left.  Then Git
will ask you to build, one last time, to confirm that the commit it selected is
actually the 'bad' commit.

The regression testing page along with the GitWine page should be all you need
to do regression testing for Wine.  That is all I used to find several
'bad' commits.

James McKenzie