On 07/05/16 08:18, Ed Maste wrote: > On 29 June 2016 at 16:35, Ed Maste <ema...@freebsd.org> wrote: >> On 29 June 2016 at 14:03, Peter Maydell <peter.mayd...@linaro.org> 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 a win for everybody. >> >> I can't speak for Sean and he's AFK for a week or two, but he's been >> performing this function for the fork for some time -- updating it for >> changes in the rest of QEMU, etc. I think we've been stuck on >> upstreaming it because it is somewhat awkward to refactor and is a >> reasonable amount of effort, and we've lacked a bsd-user maintainer to >> review or approve the patches anyhow. >> >> I agree with a large code drop being undesirable. Given current >> expectations (with bsd-user unmaintained) I hope we can make another >> push to refactor and upstream the changes. We should be able to put in >> some effort to present the patches in a sensible and logical order and >> I'm willing to help with that. Perhaps we'll need a little leeway on >> the parts specific to bsd-user, but I'm really hopeful we can make >> this happen. >> >> I also hope some folks from NetBSD, OpenBSD, DragonflyBSD and others >> will help test the patch sets.
I freely submit myself as the "weak link" here. I've been updating to QEMU master monthly in order to track and keep the patchset alive for cross building FreeBSD ports and allow folks to do cross-development. I suspect, with the exception of two recent patches submitted to the list, most, if not all of the changes outside of bsd-user are due to my ignorance of branch maintenance *or* are patches that have been languishing in the FreeBSD's pot of QEMU. To the question of CI for our version of QEMU, in a way, yes. It is used daily/weekly to build FreeBSD ports for mips, mips64 and armv6. It is being tested for armv5 and arm64/aarch64, but this is not a daily occurrence. I can branch master and setup a second "code bomb" that doesn't touch outside of bsd-user if that is something we want to move forward with. sean
signature.asc
Description: OpenPGP digital signature
