From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MRSgJ-00052Y-RM for qemu-devel@nongnu.org; Thu, 16 Jul 2009 11:15:35 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MRSgE-00051J-QG for qemu-devel@nongnu.org; Thu, 16 Jul 2009 11:15:34 -0400 Received: from [199.232.76.173] (port=38879 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MRSgE-000512-A0 for qemu-devel@nongnu.org; Thu, 16 Jul 2009 11:15:30 -0400 Received: from mx2.redhat.com ([66.187.237.31]:38979) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MRSgB-000236-5C for qemu-devel@nongnu.org; Thu, 16 Jul 2009 11:15:29 -0400 Message-ID: <4A5F438C.1000002@redhat.com> Date: Thu, 16 Jul 2009 17:13:16 +0200 From: Gerd Hoffmann MIME-Version: 1.0 Subject: Re: [Qemu-devel] [PATCH] rev5: support colon in filenames References: <1245862739.6278.7.camel@localhost> <1246063310.6278.115.camel@localhost> <1246511321.6429.31.camel@localhost> <4A4C754D.10109@redhat.com> <4A4CAD86.9020607@us.ibm.com> <4A4CB39F.5070506@redhat.com> <1247041831.6297.12.camel@localhost> <1247644283.14246.3.camel@localhost> <4A5DF252.50408@us.ibm.com> <4A5DF875.2020808@us.ibm.com> <87y6qoaglc.fsf@pike.pond.sub.org> <4A5F34EA.6020005@codemonkey.ws> In-Reply-To: <4A5F34EA.6020005@codemonkey.ws> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Anthony Liguori Cc: Kevin Wolf , Anthony Liguori , kvm-devel , linuxram@us.ibm.com, Markus Armbruster , qemu-devel@nongnu.org, Blue Swirl , Jan Kiszka , Paul Brook On 07/16/09 16:10, Anthony Liguori wrote: >> Why "-drive.ID.NAME VALUE", "-net.ID.NAME VALUE" and so forth, i.e. one >> option per object with parameters? Assuming the ID name space is flat, >> a single option suffices. What about "-set ID.NAME=VALUE"? > > Looks attractive on the surface. Feels really difficult to implement :-) Shouldn't be that horrible. Look at QemuOpts in the drive patches v3 ;) cheers, Gerd