From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:39666) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1f8RN3-0005GM-Mt for qemu-devel@nongnu.org; Tue, 17 Apr 2018 10:14:10 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1f8RN0-00078E-5d for qemu-devel@nongnu.org; Tue, 17 Apr 2018 10:14:09 -0400 Received: from mx3-rdu2.redhat.com ([66.187.233.73]:51798 helo=mx1.redhat.com) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1f8RMz-000782-WA for qemu-devel@nongnu.org; Tue, 17 Apr 2018 10:14:06 -0400 Received: from smtp.corp.redhat.com (int-mx03.intmail.prod.int.rdu2.redhat.com [10.11.54.3]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id AC4AB406E970 for ; Tue, 17 Apr 2018 14:14:05 +0000 (UTC) References: <1520839658-20499-1-git-send-email-thuth@redhat.com> <2a85941f-48bf-9e9b-0d6d-832a270d882b@redhat.com> <7413bf34-63ec-837d-d418-af2cfd1038d7@redhat.com> <87efjeaqd2.fsf@dusky.pond.sub.org> <20180417140540.GD15421@redhat.com> From: Paolo Bonzini Message-ID: <21d78c43-a6d9-95d8-ff3e-f80a9ce6b0c0@redhat.com> Date: Tue, 17 Apr 2018 16:14:02 +0200 MIME-Version: 1.0 In-Reply-To: <20180417140540.GD15421@redhat.com> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable Subject: Re: [Qemu-devel] [PATCH v2] qemu-doc: Rework the network options chapter to make "-net" less prominent List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: "=?UTF-8?Q?Daniel_P._Berrang=c3=a9?=" , Markus Armbruster Cc: Eric Blake , Thomas Huth , qemu-devel@nongnu.org, Jason Wang On 17/04/2018 16:05, Daniel P. Berrang=C3=A9 wrote: >> For what it's worth, my "[RFC PATCH 00/32] Command line QAPIfication" >> replaces the original parsing art by getopt_long_only(). >> >> Completing that work will take some time, but once it's done, we can >> (and I think we should) prefer double-dash for consistency. > Since our existing parser accepts single & double-dash already, is it > worth explicitly deprecating single-dash usage right now. So that when > your code comes along ready to merge, we're already able to say > "i told you so" and drop single-dash support at that same time. Serious questions: is _anyone_ of you actually using double-dash support in daily invocations of QEMU? Paolo