From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:55183) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VgPcW-0000JD-Bk for qemu-devel@nongnu.org; Tue, 12 Nov 2013 20:51:59 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1VgPcJ-0002t5-9H for qemu-devel@nongnu.org; Tue, 12 Nov 2013 20:51:52 -0500 Received: from mail-pa0-f42.google.com ([209.85.220.42]:45693) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VgPcJ-0002rx-37 for qemu-devel@nongnu.org; Tue, 12 Nov 2013 20:51:39 -0500 Received: by mail-pa0-f42.google.com with SMTP id kp14so7445848pab.15 for ; Tue, 12 Nov 2013 17:51:37 -0800 (PST) Message-ID: <5282DB1E.50304@ozlabs.ru> Date: Wed, 13 Nov 2013 12:51:26 +1100 From: Alexey Kardashevskiy 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> <5282217F.3050401@ozlabs.ru> <528222D8.5020606@suse.de> In-Reply-To: <528222D8.5020606@suse.de> Content-Type: text/plain; charset=UTF-8 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: =?UTF-8?B?QW5kcmVhcyBGw6RyYmVy?= , Igor Mammedov Cc: qemu-devel@nongnu.org, Jan Kiszka , Alexander Graf , Luiz Capitulino , qemu-ppc@nongnu.org, Anthony Liguori On 11/12/2013 11:45 PM, Andreas Färber wrote: > Am 12.11.2013 13:39, schrieb Alexey Kardashevskiy: >> On 12.11.2013 20:58, Igor Mammedov wrote: >>> PS: >>> 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". >> >> Heh. I do not understand movements in the qemu project most of the time >> :) I thought I could have added "compat" to PowerPC CPU as others did >> but I was so wrong :) > > Hey, I instructed you how to do exactly that, with a const char * > argument, but you chose rather to experiment more with QemuOpts. ;) > Don't blame us! :-) So instead of reusing QemuOpts infrastructure, you suggest to re-implement the parser one more time, don't you? I still cannot believe it. -- Alexey