denali wrote: > 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? Not that this matters, but I'm actually working on http://bugs.winehq.org/show_bug.cgi?id=19217 and not 19219. 19219 is someone else's bug. Oops! :)
