On 29 June 2016 at 16:22, Paolo Bonzini <pbonz...@redhat.com> 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 that. > > Neither am I. On the other hand, look at the code that we have---nobody > is using it, nobody is fixing it. Last year it stayed broken for a > month between commit ea3e98474 and commit cb48f67ad. It cannot really > be worse than the FreeBSD fork. Of course the bits outside bsd-user/ > would need proper review.
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 a win for everybody. thanks -- PMM
