wine users - Jul 2009 - Regression Testing Issue

I'm currently in the process of regression testing a bug
(http://bugs.winehq.org/show_bug.cgi?id=19219).  However, I ran into a problem
that http://www.winehq.org/docs/winedev-guide/x1348 doesn't cover.

Say a dev submits a series of patches that rely on each other for something,
such as communications.  While doing git bisect, some of those patches end up on
opposite sides of the bisect.  This renders the program unable to communicate
with the internet.  What do you do in those cases?  My solution was to issue a
git bisect good, but I'm not sure that was the best solution.  My hope is
that as I test and continue to issue git bisect good every time the program
works correctly, it'll come back around to the set of patches that are
causing the issue, but I'm unsure.

Thoughts?

denali wrote:
> Say a dev submits a series of patches that rely on each other for
something, such as communications.  While doing git bisect, some of those
patches end up on opposite sides of the bisect.  This renders the program unable
to communicate with the internet.  What do you do in those cases?
First this really shouldn't happen. All patches are required to be atomic
and not break any functionality within the series. Unfortunately this is not
always the case and some patch series do break things if not fully applied

In those cases you can use

Code:
git bisect skip


Git will pick a different commit to test. Hopefully the series that doesn't
work for you is not the source of the regression.