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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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/




_______________________________________________
Spice-devel mailing list
Spice-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.freedesktop.org/mailman/listinfo/spice-devel




[Index of Archives]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [ECOS]     [Asterisk Internet PBX]     [Linux API]     [Monitors]