From mboxrd@z Thu Jan  1 00:00:00 1970
From: Don Slutz <dslutz@verizon.com>
Subject: Re: [PATCH 1/3] cmdline_parse: Also pass bool_assert to
 OPT_CUSTOM so that parse_bool can be used correctly.
Date: Tue, 29 Jul 2014 16:05:49 -0400
Message-ID: <53D7FE9D.9080202@terremark.com>
References: <1406563175-23761-1-git-send-email-dslutz@verizon.com>
	<1406563175-23761-2-git-send-email-dslutz@verizon.com>
	<53D691420200007800026CAD@mail.emea.novell.com>
	<53D68488.3060204@terremark.com> <53D6A23A.5020702@gmail.com>
	<53D6B2DB.4080604@terremark.com>
	<53D75CCD0200007800027137@mail.emea.novell.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xen.org>
In-Reply-To: <53D75CCD0200007800027137@mail.emea.novell.com>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xen.org>
List-Help: <mailto:xen-devel-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=subscribe>
Sender: xen-devel-bounces@lists.xen.org
Errors-To: xen-devel-bounces@lists.xen.org
To: Jan Beulich <JBeulich@suse.com>, Keir Fraser <keir.xen@gmail.com>, Don Slutz <dslutz@verizon.com>
Cc: Tim Deegan <tim@xen.org>, Keir Fraser <keir@xen.org>, Ian Campbell <ian.campbell@citrix.com>, Liu Jinsong <jinsong.liu@alibaba-inc.com>, Christoph Egger <chegger@amazon.de>, Ian Jackson <ian.jackson@eu.citrix.com>, xen-devel@lists.xen.org, Stefano Stabellini <stefano.stabellini@citrix.com>, Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>, Aravind Gopalakrishnan <Aravind.Gopalakrishnan@amd.com>
List-Id: xen-devel@lists.xenproject.org


On 07/29/14 02:35, Jan Beulich wrote:
>>>> On 28.07.14 at 22:30, <dslutz@verizon.com> wrote:
>> On 07/28/14 15:19, Keir Fraser wrote:
>>> Don Slutz wrote:


> I'd say we should allow what is sensible, and reject nonsense. E.g.
> "no-" on any option that has a value (following a = separator) makes
> no sense. But custom options allowing other than boolean values
> as their value can, when no value (and no = separator) was given,
> meaningfully be prefixed by "no-", which could be resolved by the
> faked up "=no" value I was suggesting in my earlier reply (at once
> dealing with "no-" prefixes on custom options not allowing boolean
> values: their parsing routine will simply reject the faked up "no").

v2 posted with this suggestion.

    -Don Slutz

> Jan
>