From: Jeff Cody <jcody@redhat.com>
To: Max Reitz <mreitz@redhat.com>
Cc: qemu-block@nongnu.org, qemu-devel@nongnu.org,
Kevin Wolf <kwolf@redhat.com>,
Markus Armbruster <armbru@redhat.com>,
Eric Blake <eblake@redhat.com>
Subject: Re: [Qemu-devel] [PATCH for-2.8? 0/3] block/curl: Drop TFTP "support"
Date: Wed, 2 Nov 2016 14:20:04 -0400 [thread overview]
Message-ID: <20161102182004.GB15677@localhost.localdomain> (raw)
In-Reply-To: <20161102175539.4375-1-mreitz@redhat.com>
On Wed, Nov 02, 2016 at 06:55:36PM +0100, Max Reitz wrote:
> See patch 3 for the reason why we have actually never supported TFTP at
> all (except for very small files (i.e. below 256 kB or so)).
>
> I would consider this series a bug fix because, well, it doesn't really
> change any functionality, and the bug is "We don't support TFTP but we
> pretend we do".
>
I tend to agree. I'm willing to pull this in through my branch for 2.8,
unless there arises some outcry with good reason to keep tftp.
>
> Alternatives to this approach:
>
> - Deprecate TFTP first. Wait one version, then drop it.
>
> We could do this, but I personally don't think it's necessary. We have
> done this for host_floppy, but in contrast to host_floppy, TFTP really
> has never worked. Thus, I conclude that nobody is actually using it or
> has ever used it for real work.
>
> Still, if you think otherwise, we can still do this, of course.
>
>
> - Don't remove TFTP altogether, but just emit a run-time error like we
> do for HTTP servers that do not support range-based requests.
>
> Seems dirty and not like the real solution to me. Also, we have
> removed other block drivers in the past, so I don't think we should
> keep TFTP.
>
Since it is broken by nature, I like your original approach of just removing
it.
>
> Max Reitz (3):
> qemu-options: Drop mentions of curl's TFTP support
> qapi: Drop curl's TFTP protocol
> block/curl: Drop TFTP "support"
>
> block/curl.c | 20 +-------------------
> docs/qmp-commands.txt | 2 +-
> qapi/block-core.json | 7 +++----
> qemu-options.hx | 6 +++---
> 4 files changed, 8 insertions(+), 27 deletions(-)
A > 3:1 delete to insert ratio, that is an ideal patch series ;-)
next prev parent reply other threads:[~2016-11-02 18:20 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-02 17:55 [Qemu-devel] [PATCH for-2.8? 0/3] block/curl: Drop TFTP "support" Max Reitz
2016-11-02 17:55 ` [Qemu-devel] [PATCH for-2.8? 1/3] qemu-options: Drop mentions of curl's TFTP support Max Reitz
2016-11-02 18:20 ` Jeff Cody
2016-11-02 17:55 ` [Qemu-devel] [PATCH for-2.8? 2/3] qapi: Drop curl's TFTP protocol Max Reitz
2016-11-02 18:22 ` Jeff Cody
2016-11-02 17:55 ` [Qemu-devel] [PATCH for-2.8? 3/3] block/curl: Drop TFTP "support" Max Reitz
2016-11-02 18:22 ` Jeff Cody
2016-11-02 18:20 ` Jeff Cody [this message]
2016-11-03 7:56 ` [Qemu-devel] [PATCH for-2.8? 0/3] " Markus Armbruster
2016-11-04 16:53 ` Max Reitz
2016-11-07 8:20 ` Markus Armbruster
2016-11-07 15:42 ` Max Reitz
2016-11-08 7:14 ` Markus Armbruster
2016-11-09 19:15 ` Jeff Cody
2016-11-11 19:46 ` Max Reitz
2016-11-14 18:54 ` Jeff Cody
2016-11-03 9:42 ` Kevin Wolf
2016-11-07 12:57 ` [Qemu-devel] [Qemu-block] " Stefan Hajnoczi
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=20161102182004.GB15677@localhost.localdomain \
--to=jcody@redhat.com \
--cc=armbru@redhat.com \
--cc=eblake@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--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