Status updates for feature freeze

[Kevin E Martin]

On Fri, Aug 06, 2004 at 10:38:15AM -0400, Mike A. Harris wrote:
> Stuart Anderson wrote:
> >On Fri, 6 Aug 2004, Kevin E Martin wrote:
> >
> >
> >>>>>  A new section named "Extensions" was added to the configuration file:
> >>>>>
> >>>>>      Section "Extensions"
> >>>>>          Option "EXTENSION-NAME-1" "Enable"
> >>>>>          Option "EXTENSION-NAME-2" "Disable"
> >>>>>      EndSection
> >>>>>
> >>>>>  Each Option line lists one extension and a value (either "enable" or
> >>>>>  "disable").  The value is not case sensitive, but the name of the
> >>>>>  extension is (just as with the command-line options).
> >>>>
> >>>>Why not use the standard boolean option semantics instead?
> >>>
> >>>Anyone? :)
> >>
> >>We can make it anything that people want since these are just free form
> >>strings.  I'll add "on"/"off" and "true"/"false" as synonyms for
> >>"enable"/"disable".  Are there any others that people think should be
> >>added?
> >
> >
> >I think the original; question might havbe been should we be _not_
> >adding new words since there are already words in the vocabulary of the
> >config file that can be used. It seems like this might cause less
> >confusion to be more consistant.
> 
> Agreed, the config file boolean operators already support:
> 
> True/False
> Yes/No
> Option/No-option

Okay these arguments sound fine.  Please submit a patch to make this
change.