On 09/03/2018 10:11 AM, Markus Armbruster wrote:
> Kevin Wolf writes:
>
>> Am 01.09.2018 um 09:54 hat Markus Armbruster geschrieben:
>>> John Snow writes:
>>>
On 08/31/2018 02:08 AM, Markus Armbruster wrote:
> Eric Blake writes:
>
>> On 08/29/2018 08:57 PM, John Snow wrote:
Kevin Wolf writes:
> Am 01.09.2018 um 09:54 hat Markus Armbruster geschrieben:
>> John Snow writes:
>>
>> > On 08/31/2018 02:08 AM, Markus Armbruster wrote:
>> >> Eric Blake writes:
>> >>
>> >>> On 08/29/2018 08:57 PM, John Snow wrote:
>> Jobs presently use both an Error object in the
Am 01.09.2018 um 09:54 hat Markus Armbruster geschrieben:
> John Snow writes:
>
> > On 08/31/2018 02:08 AM, Markus Armbruster wrote:
> >> Eric Blake writes:
> >>
> >>> On 08/29/2018 08:57 PM, John Snow wrote:
> Jobs presently use both an Error object in the case of the create job,
>
John Snow writes:
> On 08/31/2018 02:08 AM, Markus Armbruster wrote:
>> Eric Blake writes:
>>
>>> On 08/29/2018 08:57 PM, John Snow wrote:
Jobs presently use both an Error object in the case of the create job,
and char strings in the case of generic errors elsewhere.
Unify
On 08/31/2018 02:08 AM, Markus Armbruster wrote:
> Eric Blake writes:
>
>> On 08/29/2018 08:57 PM, John Snow wrote:
>>> Jobs presently use both an Error object in the case of the create job,
>>> and char strings in the case of generic errors elsewhere.
>>>
>>> Unify the two paths as just
Eric Blake writes:
> On 08/29/2018 08:57 PM, John Snow wrote:
>> Jobs presently use both an Error object in the case of the create job,
>> and char strings in the case of generic errors elsewhere.
>>
>> Unify the two paths as just j->err, and remove the extra argument from
>> job_completed. The
On 08/29/2018 08:57 PM, John Snow wrote:
Jobs presently use both an Error object in the case of the create job,
and char strings in the case of generic errors elsewhere.
Unify the two paths as just j->err, and remove the extra argument from
job_completed. The integer error code for
