From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:60260) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VgWd3-0007H3-P6 for qemu-devel@nongnu.org; Wed, 13 Nov 2013 04:21:02 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1VgWcr-0007Gd-Eg for qemu-devel@nongnu.org; Wed, 13 Nov 2013 04:20:53 -0500 Sender: Paolo Bonzini Message-ID: <52834462.8040307@redhat.com> Date: Wed, 13 Nov 2013 10:20:34 +0100 From: Paolo Bonzini MIME-Version: 1.0 References: <1384155875-26999-1-git-send-email-aik@ozlabs.ru> <1384155875-26999-5-git-send-email-aik@ozlabs.ru> <5280D061.50802@suse.de> <20131111152546.4be13e10@thinkpad> <52816D26.3070708@ozlabs.ru> <20131112105837.63c831e6@thinkpad> In-Reply-To: <20131112105837.63c831e6@thinkpad> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Subject: Re: [Qemu-devel] [PATCH v3 4/6] qemu-option: support +foo/-foo command line agruments List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Igor Mammedov Cc: qemu-devel@nongnu.org, Alexey Kardashevskiy , Jan Kiszka , Alexander Graf , Luiz Capitulino , qemu-ppc@nongnu.org, Anthony Liguori , =?ISO-8859-1?Q?Andreas_F=E4rber?= Il 12/11/2013 10:58, Igor Mammedov ha scritto: > extending QemuOpts to parsing ±opts format, seems like good workaround > above problem. But I was under impression that general movement was to convert > custom formats to canonical format "prop=value". I think the general movement is to convert things to QemuOpts. As long as all compound options use QemuOpts, they are consistent and any syntactic sugar will apply to all in the same way. I, for one, can never remember if it is =on, =true, =yes (and interestingly =no works but =yes doesn't). So I welcome a new completely different syntax that doesn't have this problem. :) Paolo