From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: Thomas Huth <thuth@redhat.com>
Cc: "Peter Maydell" <peter.maydell@linaro.org>,
"Daniel P. Berrangé" <berrange@redhat.com>,
mszeredi@redhat.com, "QEMU Developers" <qemu-devel@nongnu.org>,
"Markus Armbruster" <armbru@redhat.com>,
"Stefan Hajnoczi" <stefanha@redhat.com>,
"Marc-André Lureau" <marcandre.lureau@redhat.com>,
vgoyal@redhat.com
Subject: Re: virtiofsd: Where should it live?
Date: Tue, 3 Dec 2019 10:53:41 +0000 [thread overview]
Message-ID: <20191203105341.GB3078@work-vm> (raw)
In-Reply-To: <fef0eaaf-149a-f8a8-02c5-821d2d42becd@redhat.com>
We seem to be coming to the conclusion something that:
a) It should live in the qemu tree
b) It shouldn't live under contrib
c) We'll create a new top level, i.e. 'daemons'
d) virtiofsd will be daemons/virtiofsd
Now, somethings I'm less clear on:
e) What else would move into daemons? It was suggested
that if we've got virtiofsd in there, then we should move
libvhost-user - which I understand, but then it's not a
'daemons'.
Are there any otehr daemons that should move?
f) Should virtiofsd always be built (if the deps are installed)?
Dave
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
next prev parent reply other threads:[~2019-12-03 11:01 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-25 18:50 virtiofsd: Where should it live? Dr. David Alan Gilbert
2019-11-26 9:02 ` Marc-André Lureau
2019-11-26 11:42 ` Dr. David Alan Gilbert
2019-11-26 10:26 ` Daniel P. Berrangé
2019-11-26 12:14 ` Dr. David Alan Gilbert
2019-12-02 10:12 ` Peter Maydell
2019-12-02 12:56 ` Markus Armbruster
2019-12-02 13:32 ` Thomas Huth
2019-12-02 15:39 ` Markus Armbruster
2019-12-02 15:55 ` Dr. David Alan Gilbert
2019-12-03 10:53 ` Dr. David Alan Gilbert [this message]
2019-12-03 11:06 ` Peter Maydell
2019-12-03 11:17 ` Dr. David Alan Gilbert
2019-12-03 11:19 ` Daniel P. Berrangé
2019-12-03 13:06 ` Dr. David Alan Gilbert
2019-12-04 7:43 ` Markus Armbruster
2019-12-04 8:17 ` Gerd Hoffmann
2019-12-04 13:28 ` Kevin Wolf
2019-12-04 13:29 ` Thomas Huth
2019-12-04 14:36 ` Eric Blake
2019-12-04 16:33 ` Dr. David Alan Gilbert
2019-12-04 12:04 ` Dr. David Alan Gilbert
2019-12-04 13:10 ` Markus Armbruster
2019-12-04 14:34 ` Eric Blake
2019-12-03 12:59 ` Paolo Bonzini
2019-12-03 13:02 ` Dr. David Alan Gilbert
2019-12-03 13:07 ` Paolo Bonzini
2019-12-03 13:10 ` Dr. David Alan Gilbert
2019-12-03 16:08 ` Greg Kurz
2019-12-02 9:37 ` Michael S. Tsirkin
2019-12-02 16:44 ` Dr. David Alan Gilbert
2019-12-02 16:52 ` Michael S. Tsirkin
2019-12-02 17:01 ` Dr. David Alan Gilbert
2019-12-02 17:16 ` Christophe de Dinechin
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=20191203105341.GB3078@work-vm \
--to=dgilbert@redhat.com \
--cc=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=mszeredi@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--cc=thuth@redhat.com \
--cc=vgoyal@redhat.com \
/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).