From: Thomas Huth <thuth@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>, Warner Losh <imp@bsdimp.com>
Cc: "Ed Maste" <emaste@freebsd.org>,
"Kamil Rytarowski" <kamil@netbsd.org>,
"QEMU Developers" <qemu-devel@nongnu.org>,
"Sean Bruno" <sbruno@freebsd.org>,
"Daniel P. Berrange" <berrange@redhat.com>,
"Alex Bennée" <alex.bennee@linaro.org>,
"Li-Wen Hsu" <lwhsu@freebsd.org>, Brad <brad@comstyle.com>
Subject: Re: qemu bsd-user plans
Date: Mon, 11 Jan 2021 13:49:33 +0100 [thread overview]
Message-ID: <b92f9183-d552-d294-89a8-d18f17c679b1@redhat.com> (raw)
In-Reply-To: <CAFEAcA-UUFng5AwFgOEKiQqR3XQEQa+pBejisuFvhUqqfxMA8Q@mail.gmail.com>
On 08/01/2021 20.56, Peter Maydell wrote:
> Adding the people to the CC list who were on the previous discussion thread...
>
> -- PMM
>
>
> On Fri, 8 Jan 2021 at 19:43, Warner Losh <imp@bsdimp.com> wrote:
[...]
>> So, my new plan is to rebase what changes I can to the tip of master and submit those for review. I'll work with the developers on the FreeBSD side to ensure they are included in reviews in addition to the normal qemu-devel list. This will allow us to pare down the deltas between our code and upstream to allow us to make progress. The changes will be held to the standard 'makes things better'. Given how broken bsd-user is today in qemu upstream, at first that will a very easy standard to make.
>>
>> The first patch I'll submit will be changing MAINTAINERS to point to me, since I'm acting as the point person in this effort. I'll then re-submit some other changes that I've submitted in the past, but CC the FreeBSD folks that are currently active (they were only CC'd to former developers who lack the time to review).
>>
>> But before I get too far down this path, I thought I'd send out what's going on to qemu-devel so I can get feedback and adjust the plan into something that's mutually agreeable so time I put towards this is not wasted.
>>
>> So, what do people think of these plans?
Sounds like a good way forward. Are you familiar with sending git pull
requests? I think once the patch to MAINTAINERS has been accepted, it's
maybe best if you send out pull request on your own once the patches got
reviewed on the mailing list - otherwise it might get cumbersome to find a
maintainers tree where the patches can go through.
Thomas
next prev parent reply other threads:[~2021-01-11 13:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-08 19:41 qemu bsd-user plans Warner Losh
2021-01-08 19:56 ` Peter Maydell
2021-01-08 20:17 ` Warner Losh
2021-01-09 17:02 ` Kyle Evans
2021-01-09 17:35 ` Warner Losh
2021-01-11 12:49 ` Thomas Huth [this message]
2021-01-11 13:27 ` Daniel P. Berrangé
2021-01-12 0:33 ` Warner Losh
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=b92f9183-d552-d294-89a8-d18f17c679b1@redhat.com \
--to=thuth@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=berrange@redhat.com \
--cc=brad@comstyle.com \
--cc=emaste@freebsd.org \
--cc=imp@bsdimp.com \
--cc=kamil@netbsd.org \
--cc=lwhsu@freebsd.org \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=sbruno@freebsd.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).