improvement to patchwatcher

[Alexandre Julliard]

"James Hawkins" <truiken at gmail.com> writes:

> On Tue, Aug 26, 2008 at 6:56 PM, Zachary Goldberg <zgold550 at gmail.com> wrote:
>>
>> 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.
>>
>
> That's not a trivial problem.  How is that useful in any way?  I can
> imagine the case where an outside user (non-developer) wants to know
> the status of a submitted patch set.  We already have wine-cvs
> archives, and source.winehq.org for that.  Everyone else can just
> update their git tree.

I think it would be quite useful. For instance it would allow sending a
nice reminder to the author to rethink/resend their patch if it hasn't
been applied after a week or so. It would also enable me (and other
reviewers) to always get an up-to-date list of patches that need to be
looked at, instead of having to keep track of it locally.

Of course that would also require other ways to take patches off the
list, for instance when an updated patch has been sent, or when someone
else fixed the bug differently. I certainly agree it's not trivial to
implement.

-- 
Alexandre Julliard
julliard at winehq.org