Open Stack

How strict is it? Does it need to be one or the other?

I'm thinking about if somebody happened to write <option>= True and
experienced a failure because of one missing space. Might be hard to
troubleshoot. Can you support both, and recommend using spaces for
readability?

Just a thought.



On Wed, Mar 12, 2014 at 5:34 AM, Phil Hopkins <phil.hopkins at rackspace.com>wrote:

> Gauvain,
>
> You are correct, that was what I was thinking and I put it in the boolean
> section. Thanks forcorrecting
> this.
>
> Phil Hopkins RHCA CMDBA
> Openstack Instructor
> Rackspace Hostingtm
> (210) 312-3584
>
> ________________________________________
> From: Gauvain Pocentek [gauvain.pocentek at objectif-libre.com]
> Sent: Tuesday, March 11, 2014 2:26 PM
> To: Phil Hopkins
> Cc: openstack-docs
> Subject: Re: [Openstack-docs] Boolean configuration options
>
> Le 2014-03-11 19:44, phil hopkins a écrit :
> > I would like to post a change to the Boolean configuration options. I
> > believe that for alll of the configuration files we should use the
> > form:
> >
> > force_dhcp_release = True
> >
> > as opposed to:
> >
> > force_dhcp_release=True
> >
> > using a space on either side of the equals sign. This makes it easier
> > to separate the configuration item and the option. I believe it is
> > easier to read.
> >
> > Any comments?
>
> +1
>
> But why limit this to boolean options? We could use this convention for
> all the options.
>
> Gauvain Pocentek
>
> Objectif Libre - Infrastructure et Formations Linux
> http://www.objectif-libre.com
>
>
> _______________________________________________
> Openstack-docs mailing list
> Openstack-docs at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs
>



-- 
/David
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-docs/attachments/20140315/1d98258f/attachment.html>