From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:49959) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fQsou-0006Y9-Kc for qemu-devel@nongnu.org; Thu, 07 Jun 2018 07:11:09 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fQsoq-0000KC-Ev for qemu-devel@nongnu.org; Thu, 07 Jun 2018 07:11:08 -0400 References: <20180426161958.2872-1-rkagan@virtuozzo.com> <20180426161958.2872-4-rkagan@virtuozzo.com> <87tvqjf28u.fsf@dusky.pond.sub.org> <3f5aaa32-5e43-542b-c657-3f1eec553e70@redhat.com> <87d0x33wyr.fsf@dusky.pond.sub.org> <19326638-6980-5473-dea9-79c7aabdf710@redhat.com> From: Thomas Huth Message-ID: Date: Thu, 7 Jun 2018 13:10:43 +0200 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH 03/17] iotests: ask qemu for supported formats List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Paolo Bonzini , Markus Armbruster Cc: Eric Blake , Roman Kagan , Kevin Wolf , qemu-devel@nongnu.org, qemu-block@nongnu.org, Max Reitz , "Daniel P. Berrange" On 07.06.2018 13:07, Paolo Bonzini wrote: > On 07/06/2018 09:50, Thomas Huth wrote: >> >>> There's no real need to kill off '?', unless it gets in the way of >>> steering people towards 'help'. We should steer them toward 'help', >>> because '?' is a trap for insufficiently sophisticated users of >>> shell[*]. >> ... and I agree with your points here. >> >> => I think we need a second list of deprecated feature (maybe we should >> call them "legacy features" instead of "deprecated"?), i.e. a list of >> features which we don't recommend for new code / scripts anymore, but >> which we do not intend to remove via our official deprecation policy any >> time soon. Things like "--enable-kvm" / "-no-kvm" or maybe even "-net" >> go into the same category. > > Yes, "-net" definitely goes there. > >> If you agree, I can try to come up with a patch (should the list go into >> qemu-doc.texi or a separate document in the the documentation folder?). > > I think it should go in docs/devel. I currently rather tend to put it into a new appendix in qemu-doc.texi, since this is useful information for the normal users, too. Or how shall we communicate this to the users that the old options that they are used to are still there, but should not be used for new scripts anymore? Thomas