Introducing patchwork, a patch review helper

Angel Ezquerra angel.ezquerra at gmail.com
Tue Jan 8 16:10:29 CST 2013


On Jan 8, 2013 9:43 PM, "Bryan O'Sullivan" <bos at serpentine.com> wrote:
>
> I spent the past day configuring an instance of the patchwork service for
Mercurial:
>
> http://patchwork.serpentine.com/
>
> This consists of three components:
> A process that dumps patches and review comments from the mailing list
into a database
> A web interface that lets people see and manage which patches are being
reviewed or ignored
> A cron job that periodically updates patches that have been committed
> Patchwork is very lightweight: http://jk.ozlabs.org/projects/patchwork/
>
> The intention is that this should make it easier for us to see which
patches need attention.
>
> If you're a regular contributor or reviewer, please consider signing up.
Especially if you resend revisions of patch series - you can mark older
patches as superseded, and help keep the queue under control.
>
> This service won't necessarily be useful to everyone, but I hope that it
will make it clearer to us as a whole when a patch series threatens to
"fall off the radar".
>
> As an example of the usefulness of patchwork, here is a patch that Sune
wrote last month that was acked by several people, but never applied:
http://patchwork.serpentine.com/patch/64/
>

Looks great!

Does it detect patches which are resent and marked as V2, V3, RESEND, etc?
You seem to imply that those must be manually handled?

Cheers,

Angel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://selenic.com/pipermail/mercurial-devel/attachments/20130108/546f04ea/attachment.html>


More information about the Mercurial-devel mailing list