From: john cooper <john@john-cooper.org>
To: Blue Swirl <blauwirbel@gmail.com>
Cc: john cooper <john.cooper@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 4/4] cpu model corrections/updates: add verbose config file handling
Date: Wed, 15 Sep 2010 01:29:01 -0400 [thread overview]
Message-ID: <4C90599D.3020406@john-cooper.org> (raw)
In-Reply-To: <AANLkTikE3gjk=icKqxQKMc0tLrpwK6JcXOFrquaKcTQX@mail.gmail.com>
Blue Swirl wrote:
> On Thu, Sep 9, 2010 at 3:48 AM, john cooper <john.cooper@redhat.com> wrote:
>>
>>> I think '?' is not very good name.
>> I agree, a shell meta char wasn't my first choice. However
>> it follows the precedent of '?' used in similar query operations
>> and was chosen only for CLI consistency.
>
> But '?' is used for other purposes: query available options. It would
> be more logical if -readconfig '?' instead could be used to query the
> default config files.
>
Which is what -writeconfig does, sort of. Although the structure
of potential multiple input config files is lost and rather the
resulting flat config space is output. But the alternative is
probably more of a headache than it's worth.
>>> Could we add flags to -readconfig,
>>> like -readconfig verbose,nodefaultconfig,file='', to match other
>>> options' syntax?
>> That seems most natural for options specific to the associated
>> config file. However the verbose flag was intended as a
>> global action rather than local to a given config file. The
>> preexisting "nodefconfig" is also a global option.
>
> Right. It just seems that there are a lot of global flags. How about
> -config nodefaults,verbose?
>
Agreed this is more logical. The reason I avoided doing so initially
was concern over impacting existing usage. But it isn't really much
in retrospect. Updated patch follows.
-john
--
john.cooper@redhat.com
next prev parent reply other threads:[~2010-09-15 5:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-07 12:31 [Qemu-devel] [PATCH 4/4] cpu model corrections/updates: add verbose config file handling john cooper
2010-09-07 18:38 ` Blue Swirl
2010-09-09 3:48 ` john cooper
2010-09-09 18:23 ` Blue Swirl
2010-09-15 5:29 ` john cooper [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-11-24 22:45 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=4C90599D.3020406@john-cooper.org \
--to=john@john-cooper.org \
--cc=blauwirbel@gmail.com \
--cc=john.cooper@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).