2017-05-11 10:07 GMT+03:00 Michal Privoznik :
> Not at all. src/remote_protocol-structs is compared to
> src/remote_protocol-structs-t3 (the former is kept within our git, the
> latter is generated on the fly) to make sure we don't break our RPC
> protocol.
>
> BTW: you can
On 05/10/2017 12:41 PM, Vasiliy Tolstov wrote:
> Hi. While i'm writing go binding for libvirt rpc api i'm parse
> src/remote/remote_protocol.x and generate needed code for go, but as i
> see libvirt have src/remote_protocol-structs file. That contains all
> needed data in mo simple syntax. But i
Hi. While i'm writing go binding for libvirt rpc api i'm parse
src/remote/remote_protocol.x and generate needed code for go, but as i
see libvirt have src/remote_protocol-structs file. That contains all
needed data in mo simple syntax. But i don't see such files for
qemu_protocol.x and