Altair <wineforum-user@xxxxxxxxxx> wrote: >Sent: Jul 21, 2010 5:23 AM >To: wine-users@xxxxxxxxxx >Subject: 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
