From: "Anders Pitman" <anders@apitman.com>
To: qemu-devel@nongnu.org
Subject: Re: Future of libslirp in QEMU
Date: Wed, 20 Apr 2022 15:18:22 -0600 [thread overview]
Message-ID: <ac3d61d4-17d0-49d4-8eb2-27e450d51928@www.fastmail.com> (raw)
In-Reply-To: <a78fd584-2d40-cbd4-95db-8a6729087a93@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1159 bytes --]
Awesome, thanks.
Apparently I'm not properly performing a date-sorted search on the list archives. I started here:
https://lists.gnu.org/archive/html/qemu-devel/
Then entered "slirp" and searched with chronological order, but the latest entry is from 2020. What am I doing wrong?
Thanks,
//anders
On Wed, Apr 20, 2022, at 2:21 PM, Daniel Henrique Barboza wrote:
>
>
> On 4/20/22 16:08, Anders Pitman wrote:
> > I noticed in the 7.0 changelog that libslirp might be removed as a submodule in the future. Since user networking is very important for my project, I'm wondering if this is simply an implementation detail, or if there are plans to eventually remove slirp support entirely from QEMU (which would be bad for me)?
> >
> > Is there somewhere I can read the discussion about this? I searched the mailing list archives but didn't see anything obvious.
>
> QEMU will still be supporting libslirp. The difference is that now QEMU will be
> using libslirp from the distro instead of packaging it itself.
>
> The relevant thread is here:
>
> https://lists.gnu.org/archive/html/qemu-devel/2022-04/msg00974.html
>
>
> Thanks,
>
>
> Daniel
>
>
[-- Attachment #2: Type: text/html, Size: 1941 bytes --]
next prev parent reply other threads:[~2022-04-20 21:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-20 19:08 Future of libslirp in QEMU Anders Pitman
2022-04-20 20:21 ` Daniel Henrique Barboza
2022-04-20 21:18 ` Anders Pitman [this message]
2022-04-21 12:57 ` Cornelia Huck
2022-04-21 11:57 ` Paolo Bonzini
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=ac3d61d4-17d0-49d4-8eb2-27e450d51928@www.fastmail.com \
--to=anders@apitman.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 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).