From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: "Daniel P. Berrangé" <berrange@redhat.com>
Cc: virtio-fs@redhat.com, slp@redhat.com, qemu-devel@nongnu.org,
stefanha@redhat.com, vgoyal@redhat.com
Subject: Re: [PATCH] Deprecate C virtiofsd
Date: Thu, 10 Feb 2022 17:27:37 +0000 [thread overview]
Message-ID: <YgVLCUE9y69iilGa@work-vm> (raw)
In-Reply-To: <YgVIxdu3/oyp3cU8@redhat.com>
* Daniel P. Berrangé (berrange@redhat.com) wrote:
> On Thu, Feb 10, 2022 at 05:13:19PM +0000, Dr. David Alan Gilbert wrote:
> > * Daniel P. Berrangé (berrange@redhat.com) wrote:
> > > On Wed, Feb 09, 2022 at 04:50:40PM +0000, Dr. David Alan Gilbert (git) wrote:
> > > > From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
> > > >
> > > > There's a nice new Rust implementation out there; recommend people
> > > > do new work on that.
> > > >
> > > > Signed-off-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
> > > > ---
> > > > docs/about/deprecated.rst | 14 ++++++++++++++
> > > > 1 file changed, 14 insertions(+)
> > > >
> > > > diff --git a/docs/about/deprecated.rst b/docs/about/deprecated.rst
> > > > index 47a594a3b6..3a0e15f8f5 100644
> > > > --- a/docs/about/deprecated.rst
> > > > +++ b/docs/about/deprecated.rst
> > > > @@ -454,3 +454,17 @@ nanoMIPS ISA
> > > >
> > > > The ``nanoMIPS`` ISA has never been upstreamed to any compiler toolchain.
> > > > As it is hard to generate binaries for it, declare it deprecated.
> > > > +
> > > > +Tools
> > > > +-----
> > > > +
> > > > +virtiofsd
> > > > +'''''''''
> > > > +
> > > > +There is a new Rust implementation of ``virtiofs`` at
> > > > +``https://gitlab.com/virtio-fs/virtiofsd``;
> > > > +since this is now marked stable, new development should be done on that
> > > > +rather than the existing C version in the QEMU tree.
> > > > +The C version will still accept fixes and patches that
> > > > +are already in development for the moment.
> > >
> > > Just to be clear, 'deprecation' is usually expected to turn into
> > > 'deletion' a minimum of 2 releases later. We are targetting the
> > > C virtiofsd to be deleted, right ? The last sentance here gives
> > > vibes that we're expecting it to stick around despite deprecation.
> >
> > I am targeting it to be deleted, but I'm expecting to give it a bit
> > more time than 2 releases; how do I do that?
>
> You can forget to remove it after 2 releases, which is what
> happens with many deprecations :-) '2' is really just the
> minimum bar in practice.
OK, I can remember to forget.
Dave
> 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 :|
>
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
prev parent reply other threads:[~2022-02-10 18:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-09 16:50 [PATCH] Deprecate C virtiofsd Dr. David Alan Gilbert (git)
2022-02-09 20:02 ` Vivek Goyal
2022-02-09 20:47 ` Peter Maydell
2022-02-10 17:07 ` Dr. David Alan Gilbert
2022-02-10 8:57 ` Daniel P. Berrangé
2022-02-10 17:13 ` Dr. David Alan Gilbert
2022-02-10 17:17 ` Daniel P. Berrangé
2022-02-10 17:27 ` Dr. David Alan Gilbert [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=YgVLCUE9y69iilGa@work-vm \
--to=dgilbert@redhat.com \
--cc=berrange@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=slp@redhat.com \
--cc=stefanha@redhat.com \
--cc=vgoyal@redhat.com \
--cc=virtio-fs@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).