On 03/26/2018 01:39 PM, Max Reitz wrote:
Hi,
iotests 209 and 123 fail under 32-bit (or at least with -m32), both with
gcc and mingw.
Diff for 209:
@@ -1,2 +1,2 @@
-[{ "start": 0, "length": 524288, "depth": 0, "zero": false, "data": true},
-{ "start": 524288, "length": 524288, "depth": 0, "zero
Hi,
iotests 209 and 123 fail under 32-bit (or at least with -m32), both with
gcc and mingw.
Diff for 209:
@@ -1,2 +1,2 @@
-[{ "start": 0, "length": 524288, "depth": 0, "zero": false, "data": true},
-{ "start": 524288, "length": 524288, "depth": 0, "zero": true, "data":
false}]
+qemu-img: Protoco
On 11/10/2017 10:51 AM, Vladimir Sementsov-Ogievskiy wrote:
> 10.11.2017 19:06, Eric Blake wrote:
>> On 11/09/2017 06:42 AM, Vladimir Sementsov-Ogievskiy wrote:
>>> Hi!
>>>
>>> Interesting fact: list/set_meta_context options are per-export,
>>> so, in the server we should keep context selection per
10.11.2017 19:06, Eric Blake wrote:
On 11/09/2017 06:42 AM, Vladimir Sementsov-Ogievskiy wrote:
Hi!
Interesting fact: list/set_meta_context options are per-export,
so, in the server we should keep context selection per client per export.
And it is possible for client to set contexts for one ex
On 11/09/2017 06:42 AM, Vladimir Sementsov-Ogievskiy wrote:
> Hi!
>
> Interesting fact: list/set_meta_context options are per-export,
> so, in the server we should keep context selection per client per export.
>
> And it is possible for client to set contexts for one export and than
> proceed
> t
Hi!
Interesting fact: list/set_meta_context options are per-export,
so, in the server we should keep context selection per client per export.
And it is possible for client to set contexts for one export and than
proceed
to transmission phase with another one.
This is not really touched in spe
