Am 31.07.2013 14:33, schrieb Laszlo Ersek:
> On 07/31/13 10:50, Markus Armbruster wrote:
>> Markus Armbruster writes:
>>
>>> Ping?
>>
>> Has been ignored for six weeks, and now it no longer applies. Rebased
>> version coming.
>>
>> *Sigh*
>
> Why haven't you been made a maintainer yet? You could
On 07/31/13 10:50, Markus Armbruster wrote:
> Markus Armbruster writes:
>
>> Ping?
>
> Has been ignored for six weeks, and now it no longer applies. Rebased
> version coming.
>
> *Sigh*
Why haven't you been made a maintainer yet? You could have a
"cleanup-fubars" tree and you could send pull
Markus Armbruster writes:
> Ping?
Has been ignored for six weeks, and now it no longer applies. Rebased
version coming.
*Sigh*
Ping?
Markus Armbruster writes:
> All I wanted to do is exit(1) instead of abort() on guest memory
> allocation failure [07/08]. But that lead me into a minor #ifdef bog,
> and here's what I brought back. Enjoy!
>
> Testing:
> * Christian Borntraeger reports v1 works fine under LPAR (new S390
On 06/20/2013 09:54 AM, Markus Armbruster wrote:
> All I wanted to do is exit(1) instead of abort() on guest memory
> allocation failure [07/08]. But that lead me into a minor #ifdef bog,
> and here's what I brought back. Enjoy!
>
> Testing:
> * Christian Borntraeger reports v1 works fine under
All I wanted to do is exit(1) instead of abort() on guest memory
allocation failure [07/08]. But that lead me into a minor #ifdef bog,
and here's what I brought back. Enjoy!
Testing:
* Christian Borntraeger reports v1 works fine under LPAR (new S390
KVM, i.e. generic allocation) and as second
