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]

 



On Thu, Jul 27, 2017 at 03:24:52PM +0200, Christophe de Dinechin wrote:
> Here is a recent example. For the work on the streaming agent, I recently
> ran into a compilation error because spice-prootocol was not the “right one”
> for the code being reviewed, which was IIRC in the spice server. It turns out
> that the only one I found that was “right” was some personal branch that
> Frediano has somewhere.
> 
> How does git remote add/update help solve that, when the problem was
> precisely to find the remote and branch?

There was only one version of streaming agent patches sent, and there
was one series for spice-protocol, and one for the spice-server. I'd
expect they work together. If you are talking about testing
experimental code being developed by multiple persons, then yes, you
might have to do a bit of hunting to pick up the right branch. Just
ping/ask someone more closely involved, they should be able togive you
the right pointers :)

Christophe

Attachment: signature.asc
Description: PGP signature

_______________________________________________
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]