[Spice-devel] Proposal: review branches (was Re: [vdagent-win PATCH v6 2/5] Initial rewrite of image conversion code)

[Frediano Ziglio]

> 
> Hi
> 
> ----- Original Message -----
> > ...
> > 
> > > 
> > > > > 3. If you want to test, a git checkout is enough to test (assuming
> > > > > you
> > > > > did
> > > > > the git fetch above). Simpler IMO than git am (even if I assume most
> > > > > of
> > > > > us
> > > > > have scripts to process incoming mail)
> > > 
> > > qemu uses patchew, I think it would be worth to consider it for spice as
> > > well. It applies the patches on a mailing list, run some tests, gives you
> > > a
> > > stable URL, tracks the review (and the various iteration recently
> > > iirc)...
> > > 
> > 
> > How difficult is to setup and maintain patchew?
> > Can be setup on a cloud?
> > Different people here are quite good with Gitlab and using PR Gitlab I
> > think would be easier.
> 
> If the primary mean to do patch review is through ML (which I prefer
> personally), then patchew is a worth complementary tool.
> 
> I don't know how hard it is to set up, but there is a link to request adding
> new projects on http://patchew.org/
> 

Looks interesting but looks more like an improved version of patchwork
adding test support and some additional notification.
Looking at the feature list there's nothing that seems to help with
old series tracking. For instance looking at Qemu patches
(http://patchew.org/QEMU/) there's no status of the merge. Maybe
there are more option if you log in but I think the status should
be visible (and editable by maintainers).

Frediano