<br><br><div class="gmail_quote">2010/2/16 André Hentschel <span dir="ltr"><<a href="mailto:nerv@dawncrow.de" target="_blank">nerv@dawncrow.de</a>></span><br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
Just some ideas by me:<br>
<br>
<br>
<br>
Dan Kegel schrieb:<br>
<div>> Seth Shelnutt wrote:<br>
>> I am wondering what that status of patchwatcher is?<br>
><br>
> It's waiting around for somebody to have time to start it<br>
> up again. It's ugly code, written in shell and perl, which<br>
> scares most people off. One has to wonder whether it<br>
> shouldn't be done over again using buildbot, just to avoid<br>
> scaring people. But it could live on in its present form<br>
> given time and attention. Another problem is that the<br>
> code for watching for patch series is fragile. We might<br>
> conceivably move to driving it from a web submission form<br>
> like WineTestBot uses, that would solve that.<br>
<br>
</div>maybe we can merge patchwatcher with <a href="http://source.winehq.org/patches/" target="_blank">http://source.winehq.org/patches/</a> or let it just parse it and let patchwatcher run on an extra winetestbot machine??<br>
<br>
<br>
</blockquote></div><br>Well in that case then, perhaps an entire GSoC project could be devoted to patchwatcher and getting it running again? I would be interested in doing such a thing. I will download the code from your google site (I assume that is the latest code?), and start having some fun with it to get myself acquainted.<br>
<br><br>Thanks,<br><br>Seth Shelnutt <br>