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

Marc-André Lureau marcandre.lureau at redhat.com
Fri Jul 28 11:37:04 UTC 2017



----- Original Message -----
> > 
> > Hi
> > 
> > ----- Original Message -----
> > 
> > > If you are worried about more effort for PRs considering the solution
> > > 2 could be an option. If patchew is able to create an "item" (actually
> > > I think they call them just "series") and you are able to see the
> > > merge status and change it if needed you hardly will forget a series.
> > 
> > I agree, and even before a series exist, it is useful to keep track of the
> > discussion/feature state, and there is bugzilla (and the wiki) for that.
> > 
> > https://bugs.freedesktop.org/buglist.cgi?cmdtype=runnamed&list_id=620536&namedcmd=spice
> 
> This gives me "The search named spice does not exist.".

Oh sorry, this is my personal filter, but you get the point

https://bugs.freedesktop.org/buglist.cgi?list_id=620547&product=Spice&resolution=---

> 
> > https://www.spice-space.org/page/In_progress
> > 
> > For instance, the seamless series is really not "lost", if only people keep
> > using bugzilla:
> > https://bugs.freedesktop.org/show_bug.cgi?id=39238
> 
> Are you suggesting to open a bug report for every patch send to
> the ML?

No, as I said before, I think if the submitter doesn't even bother to ping on his own patch or series, it is basically abandoned (until somehow does some research on the topic).

So if you want to make sure it is being tracked somehow, open a bug. Spice developers should refresh/update their open bugs regularly.

> 
> > 
> > I am hardly convinced adding yet another way to track things will improve
> > the
> > situation, quite the contrary.
> > 
> 
> These ways seems far from the series/patches level we are mainly
> discussing.

Ok, then you lost me :)


More information about the Spice-devel mailing list