From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Warner Losh <imp@bsdimp.com>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: bsd-user: Dropping the NetBSD and OpenBSD code
Date: Fri, 6 Feb 2026 08:31:08 +0000 [thread overview]
Message-ID: <aYWmzBy9TMQd0cra@redhat.com> (raw)
In-Reply-To: <CANCZdfq74R8fLc9+NURynkKz+D1FOtxKRGno9EwjN--hPpdf6Q@mail.gmail.com>
On Thu, Feb 05, 2026 at 06:03:56PM -0700, Warner Losh wrote:
> So, it's been years since this code compiled by default, and even more
> years since they compiled at all.
>
> Maybe 5 years ago, I contacted the OpenBSD folks, who said it had decayed
> beyond uselessness. So I plan on just removing the bsd-user/openbsd code
> shortly.
>
> Maybe 4 years ago, someone from NetBSD popped up and said they had a fork
> and they'd share it with me, but they never did, and we never reconnected
> despite some email attempts since then. So, I'd like to remove the netbsd
> directory as well.
>
> Both of these are finally getting enough in the way that they are causing
> me problems with upstreaming the bsd-user stuff. Now that I have a good
> head of steam on doing that, I'd like to finish that process. Expect me to
> flood your email in the coming months with way too many patches now that
> I've found a way to streamline the process enough for me to sneak it into
> what would otherwise be lost Friday afternoons...
>
> Before I send the patch series to do this, I'd like to do a last and final
> call for collaboration. I kept it around for this long in the hopes someone
> would show up, but nobody ever did.
We probably should have marked the feature deprecated a while ago, but since
you indicate it can't even compile, I think that's sufficient justification
to simply delete it. The period of time when it failed to compile can be
considered to count as the deprecation count down
Personally I'd suggest just sending the patches to do the deletion, and
CC'ing the relevant people on those. An actual deletion proposal is more
likely to wake any interested person from their slumber. If someone does
show up we can debate whether to none the less go ahead with deletion,
and let someone pull it back out of git history later if they want to
work on making it build again.
With regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
prev parent reply other threads:[~2026-02-06 8:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-06 1:03 bsd-user: Dropping the NetBSD and OpenBSD code Warner Losh
2026-02-06 7:41 ` Thomas Huth
2026-02-06 8:31 ` Daniel P. Berrangé [this message]
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=aYWmzBy9TMQd0cra@redhat.com \
--to=berrange@redhat.com \
--cc=imp@bsdimp.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.