On Sat, Apr 17, 2010 at 6:34 AM, Thomas Keller
<address@hidden> wrote:
This is only partially a problem of the hook. The options system simply
has no general code to accept --no-<something> options which would
switch the default of the --<something> value to the opposite.
Allowing a general --no-foo for each boolean option --foo would probably be a good thing though. It would be nice if any early --no-files option could be overridden by a later --files option. Ditto for --no-merges --no-graph, etc. This may not make sense for every boolean option that we have, but it would for many of them.
Cheers,
Derek