From: Paolo Bonzini <pbonzini@redhat.com>
To: Ed Maste <emaste@freebsd.org>, Markus Armbruster <armbru@redhat.com>
Cc: qemu-devel <qemu-devel@nongnu.org>,
Peter Maydell <peter.maydell@linaro.org>,
mark.cave-ayland@ilande.co.uk
Subject: Re: [Qemu-devel] [PATCH 3/2] MAINTAINERS: Remove Blue Swirl leftovers
Date: Wed, 29 Jun 2016 15:32:57 +0200 [thread overview]
Message-ID: <714a39c6-5fe1-f23c-bca3-f5deb3a6f098@redhat.com> (raw)
In-Reply-To: <CAPyFy2CRDEfBxrjP4ahhH6c07PdKh3iXZ9Ahp84r0WPfoDT07g@mail.gmail.com>
On 29/06/2016 15:24, Ed Maste wrote:
> On 20 June 2016 at 10:19, Markus Armbruster <armbru@redhat.com> 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 after it.
>
> Note that we are still very interested in having the BSD user
> refactoring and improvements upstream, and are not interested in
> indefinitely carrying around a fork. We do need to figure out how to
> effectively restart the effort to upstream the work.
>
> The bsd-user work is stable and usable. We use it to cross-build more
> than 20,000 packages of third-party software in the FreeBSD ports
> collection.
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...
Paolo
next prev parent reply other threads:[~2016-06-29 13:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-15 7:25 [Qemu-devel] [PATCHv3 0/2] MAINTAINERS: update entries for SPARC Mark Cave-Ayland
2016-06-15 7:25 ` [Qemu-devel] [PATCHv3 1/2] MAINTAINERS: add Artyom Tarasenko as SPARC maintainer Mark Cave-Ayland
2016-06-15 7:25 ` [Qemu-devel] [PATCHv3 2/2] MAINTAINERS: remove Blue Swirl " Mark Cave-Ayland
2016-06-20 14:19 ` [Qemu-devel] [PATCH 3/2] MAINTAINERS: Remove Blue Swirl leftovers Markus Armbruster
2016-06-29 13:24 ` Ed Maste
2016-06-29 13:32 ` Paolo Bonzini [this message]
2016-06-29 15:10 ` Peter Maydell
2016-06-29 15:22 ` Paolo Bonzini
2016-06-29 18:03 ` Peter Maydell
2016-06-29 20:35 ` Ed Maste
2016-06-29 20:55 ` Ed Maste
[not found] ` <CAPyFy2DtwsYhPeZfsNST3Xh3Et9ie3PyVeoD9B5=UQPd_uqzTw@mail.gmail.com>
2016-07-05 14:31 ` Sean Bruno
2016-06-29 18:23 ` Alex Bennée
2016-06-30 12:35 ` Peter Maydell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=714a39c6-5fe1-f23c-bca3-f5deb3a6f098@redhat.com \
--to=pbonzini@redhat.com \
--cc=armbru@redhat.com \
--cc=emaste@freebsd.org \
--cc=mark.cave-ayland@ilande.co.uk \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).