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

[Marc-André Lureau]

Hi

----- Original Message -----
> > 
> > > > Imho, we could benefit using a system tracking patch series state from
> > > > the
> > > > mailing list, such as patchew. But it would probably need some work to
> > > > fit
> > > > Spice needs.
> > > 
> > > We would benefit from that, yes. But that’s another issue entirely.
> > 
> > If the issue is about tracking patch series state, then it's not not
> > entirely
> > different.
> > 
> 
> The "not not" is not clear. What the advantage in regards of patch tracking
> compared to patchwork?

"not not" :)

Indeed, patchew and patchworks share a lot of similarities

Advantages over patchworks from my user pov:
- it's being used by qemu & libvirt, so quite close to spice teams/practices
- it applies patches and run tests (somewhat covered by other CI, but here over ML)
- it gives a GIT url for the series (if it applied correctly) - nice!
- it is able to diff between revisions (ex: http://patchew.org/series-diff/20170724164601.21063-1-berrange@redhat.com/20170727113243.23991-1-berrange@redhat.com/)
- I find the patchew web interface slightly more convenient, a matter of taste perhaps

But patchworks has some command line interface iirc, I don't know if they exist for patchew, but the GIT url is usually all I really need