John Snow writes:
> On 04/18/2018 03:25 AM, Markus Armbruster wrote:
>> John Snow writes:
>>
>>> On 04/17/2018 09:44 AM, Markus Armbruster wrote:
John Snow writes:
> This series seeks to address two distinct but closely related issues
> concerning the job management API.
On 04/18/2018 03:25 AM, Markus Armbruster wrote:
> John Snow writes:
>
>> On 04/17/2018 09:44 AM, Markus Armbruster wrote:
>>> John Snow writes:
>>>
This series seeks to address two distinct but closely related issues
concerning the job management API.
(1) For jobs that com
John Snow writes:
> On 04/17/2018 09:44 AM, Markus Armbruster wrote:
>> John Snow writes:
>>
>>> This series seeks to address two distinct but closely related issues
>>> concerning the job management API.
>>>
>>> (1) For jobs that complete when a monitor is not attached and receiving
>>> ev
On 04/17/2018 09:44 AM, Markus Armbruster wrote:
> John Snow writes:
>
>> This series seeks to address two distinct but closely related issues
>> concerning the job management API.
>>
>> (1) For jobs that complete when a monitor is not attached and receiving
>> events or notifications, ther
Forgot to mention: yes, I know this has been merged already. I'm merely
trying to catch up with recent block layer progress.
John Snow writes:
> This series seeks to address two distinct but closely related issues
> concerning the job management API.
>
> (1) For jobs that complete when a monitor is not attached and receiving
> events or notifications, there's no way to discern the job's final
> return code. Job
Hi,
This series seems to have some coding style problems. See output below for
more information:
Type: series
Message-id: 20180310082746.24198-1-js...@redhat.com
Subject: [Qemu-devel] [PATCH v5 00/21] blockjobs: add explicit job management
=== TEST SCRIPT BEGIN ===
#!/bin/bash
BASE=base
n=1
tot