On 07/05/16 08:18, Ed Maste wrote:
> On 29 June 2016 at 16:35, Ed Maste wrote:
>> On 29 June 2016 at 14:03, Peter Maydell wrote:
>>>
>>> I think from an upstream-maintainer viewpoint the question is
>>> whether a code drop would be just a code drop, or whether
>>> it gets us to a position where
On 20 June 2016 at 15:19, Markus Armbruster wrote:
> Blue hasn't been active in the QEMU project for a long time. Drop his
> last MAINTAINERS entries.
>
> As per Paolo's recommendation, downgrade status of "BSD user" from
> Maintained to Orphan since the FreeBSD guys effectively forked it, and
>
On 29 June 2016 at 16:35, Ed Maste wrote:
>
> I agree with a large code drop being undesirable.
Here's a little more information for reference.
Sean's qemu-bsd-user branch is here: https://github.com/seanbruno/qemu-bsd-user
The last upstream merge was from commit d6550e9e about a month ago.
Dif
On 29 June 2016 at 14:03, Peter Maydell wrote:
>
> I think from an upstream-maintainer viewpoint the question is
> whether a code drop would be just a code drop, or whether
> it gets us to a position where we have an active upstream
> maintainer for the bsd-user code. I think the latter would
> be
Paolo Bonzini writes:
> On 29/06/2016 17:10, Peter Maydell wrote:
>>> Honestly I'm wondering if a huge code drop could be the right solution
>>> here. It's not how we usually do things, but rules exist to be broken...
>>
>> I can't say I'm really enthusiastic about doing that.
>
> Neither am I.
On 29 June 2016 at 16:22, Paolo Bonzini wrote:
> On 29/06/2016 17:10, Peter Maydell wrote:
>>> Honestly I'm wondering if a huge code drop could be the right solution
>>> here. It's not how we usually do things, but rules exist to be broken...
>>
>> I can't say I'm really enthusiastic about doing
On 29/06/2016 17:10, Peter Maydell wrote:
>> Honestly I'm wondering if a huge code drop could be the right solution
>> here. It's not how we usually do things, but rules exist to be broken...
>
> I can't say I'm really enthusiastic about doing that.
Neither am I. On the other hand, look at the
On 29 June 2016 at 14:32, Paolo Bonzini wrote:
> Honestly I'm wondering if a huge code drop could be the right solution
> here. It's not how we usually do things, but rules exist to be broken...
I can't say I'm really enthusiastic about doing that.
thanks
-- PMM
On 29/06/2016 15:24, Ed Maste wrote:
> On 20 June 2016 at 10:19, Markus Armbruster wrote:
>>
>> As per Paolo's recommendation, downgrade status of "BSD user" from
>> Maintained to Orphan since the FreeBSD guys effectively forked it, and
>> "SPARC target" from Maintained to Odd Fixes, since we st
On 20 June 2016 at 10:19, Markus Armbruster wrote:
>
> As per Paolo's recommendation, downgrade status of "BSD user" from
> Maintained to Orphan since the FreeBSD guys effectively forked it, and
> "SPARC target" from Maintained to Odd Fixes, since we still have the
> overall TCG maintainer looking
Blue hasn't been active in the QEMU project for a long time. Drop his
last MAINTAINERS entries.
As per Paolo's recommendation, downgrade status of "BSD user" from
Maintained to Orphan since the FreeBSD guys effectively forked it, and
"SPARC target" from Maintained to Odd Fixes, since we still hav
11 matches
Mail list logo
