On 7 July 2015 at 14:08, Juan Quintela wrote:
> Hi
>
> [v3]
> - make migration events disabled by default with a capability
> make check failed because its parser is wrong, but I haven't been able to
> fix it.
>
> Once here, is there a good reason why a parser needs to read char by
> char f
Hi
[v3]
- make migration events disabled by default with a capability
make check failed because its parser is wrong, but I haven't been able to fix
it.
Once here, is there a good reason why a parser needs to read char by
char from the network and try a json parser each single time in
201
