improvement to patchwatcher

[Zachary Goldberg]

On Tue, Aug 26, 2008 at 4:39 PM, James Hawkins <truiken at gmail.com> wrote:
> On Tue, Aug 26, 2008 at 3:28 PM, Vijay Kiran Kamuju <infyquest at gmail.com> wrote:
>> Hi,
>>
>> Is it possible to add column to the patchwatcher, whether the patch
>> has been rejected/accepted/pending into git.
>>
>
> This is extending patchwatcher too far, and it puts an unnecessary
> burden on Alexandre to reply to the system.  In my experience, and not
> just with my patches, there is rarely a pending state for a patch.
> There is often an "I'm not sure about it" state, but that basically
> means the patch is rejected.  The point of patchwatcher is to help the
> patch submitter in that he can quickly see if some of the basic
> requirements of a patch are not fulfilled (things he should be
> checking anyway).
>
>> Also please skip the mail entries if they do have "Re:" in the subject
>> and do not have any patch.
>> Mark the corresponding patch to rejected/needs more work.
>>
>
> This has already been discussed:
>
> http://winehq.org/pipermail/wine-devel/2008-August/068452.html
>
> --
> James Hawkins
>
>
>

Would it be difficult though to once a day do a git fetch and attempt
to re-apply all the known (good) patches to see if they've fail with
patch errors (==been committed)?   That seems like it might be useful.