OK, I've checked in the updated Patchwatcher source http://code.google.com/p/winezeug/source/detail?r=177 and have turned email notifications back on.
I also told it to rerun the most recent 11 patches, just to test that it's sending the good patches to http://groups.google.com/group/wine-patches-filtered again.
The results page http://kegel.com/wine/patchwatcher/results/ looks nice and green; the blacklist at http://winezeug.googlecode.com/svn/trunk/patchwatcher/blacklist.txt filters out all the tests that tend to fail on my test machine infrequently enough that they show up in the five baseline test runs, but frequently enough that they caused bogus failure reports in the few hundered patches I've processed.
It would be *very good* to whittle that blacklist down to zero. I should update http://bugs.winehq.org/show_bug.cgi?id=9916 with a script that runs just the problematic tests over and over again. (Or maybe I should start a new bug, that one is pretty long.)
On Fr, 2008-09-05 at 10:24 -0700, Dan Kegel wrote:
The results page http://kegel.com/wine/patchwatcher/results/ looks nice and green;
Opps, all developer send there Patches in September with "09" as minute, and in August with "08" ...
:-)
And it would be very nice, when you hide the Email-Address to block the bots, who collect spam targets.
On Tue, Sep 9, 2008 at 11:37 AM, Detlef Riekenberg wine.dev@web.de wrote:
Opps, all developer send there Patches in September with "09" as minute, and in August with "08" ...
Whoops!
And it would be very nice, when you hide the Email-Address to block the bots, who collect spam targets.
Is that needed, given how the addresses are in the open on the mailing list and all its archives?
2008/9/9 Dan Kegel dank@kegel.com:
And it would be very nice, when you hide the Email-Address to block the bots, who collect spam targets.
Is that needed, given how the addresses are in the open on the mailing list and all its archives?
I doubt it, we're probably on every possible spam list anyway.