Niels de Vos writes:
> On Tue, Jan 08, 2019 at 08:12:16PM +0100, Kevin Wolf wrote:
>> Am 08.01.2019 um 18:18 hat Markus Armbruster geschrieben:
>> > This patch series got stuck.
>> >
>> > Markus Armbruster writes:
>> >
>> > > Fam Zheng writes:
>> > >
>> > >> On Tue, 09/25 07:00, Markus
Thomas Huth writes:
> On 2019-01-08 20:12, Kevin Wolf wrote:
>> Am 08.01.2019 um 18:18 hat Markus Armbruster geschrieben:
>>> This patch series got stuck.
>>>
>>> Markus Armbruster writes:
>>>
Fam Zheng writes:
> On Tue, 09/25 07:00, Markus Armbruster wrote:
>> Jeff Cody
On Tue, Jan 08, 2019 at 08:12:16PM +0100, Kevin Wolf wrote:
> Am 08.01.2019 um 18:18 hat Markus Armbruster geschrieben:
> > This patch series got stuck.
> >
> > Markus Armbruster writes:
> >
> > > Fam Zheng writes:
> > >
> > >> On Tue, 09/25 07:00, Markus Armbruster wrote:
> > >>> Jeff Cody
On 2019-01-08 20:12, Kevin Wolf wrote:
> Am 08.01.2019 um 18:18 hat Markus Armbruster geschrieben:
>> This patch series got stuck.
>>
>> Markus Armbruster writes:
>>
>>> Fam Zheng writes:
>>>
On Tue, 09/25 07:00, Markus Armbruster wrote:
> Jeff Cody writes:
>
>> I'll not be
Am 08.01.2019 um 18:18 hat Markus Armbruster geschrieben:
> This patch series got stuck.
>
> Markus Armbruster writes:
>
> > Fam Zheng writes:
> >
> >> On Tue, 09/25 07:00, Markus Armbruster wrote:
> >>> Jeff Cody writes:
> >>>
> >>> > I'll not be involved in day-to-day qemu development.
This patch series got stuck.
Markus Armbruster writes:
> Fam Zheng writes:
>
>> On Tue, 09/25 07:00, Markus Armbruster wrote:
>>> Jeff Cody writes:
>>>
>>> > I'll not be involved in day-to-day qemu development. Remove
>>> > myself as maintainer from the remainder of the network block
On Tue, Sep 25, 2018 at 03:49:36PM +0800, Fam Zheng wrote:
> On Tue, 09/25 09:37, Markus Armbruster wrote:
> > Do we want to have a dedicated VHDX driver submaintainer again? Fam,
> > you're maintaining VMDK, could you cover VHDX as well?
>
> I don't know a lot VHDX internals. Considering my
On Tue, 09/25 09:37, Markus Armbruster wrote:
> Do we want to have a dedicated VHDX driver submaintainer again? Fam,
> you're maintaining VMDK, could you cover VHDX as well?
I don't know a lot VHDX internals. Considering my capacity at the moment I'd
rather not take this one.
Fam
Fam Zheng writes:
> On Tue, 09/25 07:00, Markus Armbruster wrote:
>> Jeff Cody writes:
>>
>> > I'll not be involved in day-to-day qemu development. Remove
>> > myself as maintainer from the remainder of the network block drivers
>> > (and vhdx), and revert them to the general block layer
On Tue, Sep 25, 2018 at 01:32:04PM +0800, Fam Zheng wrote:
> On Tue, 09/25 07:00, Markus Armbruster wrote:
> > Jeff Cody writes:
> >
> > > I'll not be involved in day-to-day qemu development. Remove
> > > myself as maintainer from the remainder of the network block drivers
> > > (and vhdx), and
On Tue, 09/25 07:00, Markus Armbruster wrote:
> Jeff Cody writes:
>
> > I'll not be involved in day-to-day qemu development. Remove
> > myself as maintainer from the remainder of the network block drivers
> > (and vhdx), and revert them to the general block layer maintainership.
> >
> >
Jeff Cody writes:
> I'll not be involved in day-to-day qemu development. Remove
> myself as maintainer from the remainder of the network block drivers
> (and vhdx), and revert them to the general block layer maintainership.
>
> Signed-off-by: Jeff Cody
> ---
> MAINTAINERS | 14 --
12 matches
Mail list logo