From: john cooper <john.cooper@redhat.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: Mark McLoughlin <markmc@redhat.com>,
KVM list <kvm@vger.kernel.org>,
"Przywara, Andre" <Andre.Przywara@amd.com>,
john.cooper@redhat.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] Add assignment operation to config file parser..
Date: Mon, 08 Feb 2010 11:00:54 -0500 [thread overview]
Message-ID: <4B703536.2070801@redhat.com> (raw)
In-Reply-To: <4B700FE7.7020009@redhat.com>
Gerd Hoffmann wrote:
> On 02/07/10 17:24, Anthony Liguori wrote:
>> On 02/06/2010 12:59 PM, john cooper wrote:
>>> This patch reworks support for both assignment and
>>> append in the config file parser. It was motivated
>>> by comments received on the cpu model config file
>>> format.
>>>
>>> Commit dc9ca4ba27be4fe6a0284061b8f056c4364fb0d9
>>> changed the behavior of "=" from assign to append.
>>> This patch preserves the ability to append to an
>>> option (however now via "+="), reverts "=" to its
>>> previous behavior, and allows both to interoperate.
>>>
>>> Signed-off-by: john cooper<john.cooper@redhat.com>
>>
>> This deviates from standard ini syntax which makes me a big
>> uncomfortable with it. Gerd, do you have an opinion?
>
> Also it the syntax change will break existing users of the append
> feature (host/guestfwd for slirp networking).
>
> Any reason why you can't use the current append to avoid the overlong
> feature flag lines?
Impacting existing usage was my primary concern as well.
I'd run this by Mark who created the patch changing the
disposition of "=" to append and I didn't find any alarms
there.
The proposed scheme supports both semantics and arguably
seems more intuitive. If that is the general consensus
and it won't unduly perturb existing usage the above
would be opportune before the current behavior becomes
more entrenched (e.g. by further dependencies such as the
proposed cpu model configuration).
But to answer the question, my prior patch can work with
either.
Thanks,
-john
--
john.cooper@redhat.com
next prev parent reply other threads:[~2010-02-08 16:09 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-01 19:02 [Qemu-devel] [PATCH] Add cpu model configuration support.. (resend) john cooper
2010-02-02 10:17 ` [Qemu-devel] " Andre Przywara
2010-02-02 11:07 ` Andre Przywara
2010-02-02 19:34 ` john cooper
2010-02-06 18:59 ` [Qemu-devel] [PATCH] Add assignment operation to config file parser john cooper
2010-02-07 16:24 ` Anthony Liguori
2010-02-08 13:21 ` Gerd Hoffmann
2010-02-08 16:00 ` john cooper [this message]
2010-06-09 8:05 ` [Qemu-devel] [PATCH] Add optional dump of default config file paths john cooper
2010-06-14 17:01 ` Anthony Liguori
2010-06-14 17:07 ` Daniel P. Berrange
2010-06-14 17:59 ` john cooper
2010-06-14 19:13 ` Anthony Liguori
2010-02-10 20:00 ` [Qemu-devel] [PATCH] Add cpu model configuration support.. (resend) Anthony Liguori
2010-02-14 6:52 ` john cooper
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4B703536.2070801@redhat.com \
--to=john.cooper@redhat.com \
--cc=Andre.Przywara@amd.com \
--cc=kraxel@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=markmc@redhat.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).