Re: How to undo previously set configuration? (again)
- Date: Thu, 25 Apr 2019 07:36:14 -0700
- From: Jonathan Nieder <jrnieder@xxxxxxxxx>
- Subject: Re: How to undo previously set configuration? (again)
Ævar Arnfjörð Bjarmason wrote:
> Because we don't have some general config facility for this it keeps
> coming up, and various existing/proposed options have their own little
> custom hacks for doing it, e.g. this for Barret Rhoden's proposed "blame
> skip commits" feature
> (b.t.w. I *meant* /dev/null in that E-Mail, but due to PEBCAK wrote
I'm confused. Isn't that bog-standard Git usage, not a custom hack?
That is, I thought the intended behavior is always
1. For single-valued options, last value wins.
2. For multi-valued options, empty clears the list.
3. When there is a special behavior triggered by not supplying the
option at all, offer an explicit value like "default" that triggers
the same behavior, too.
and that any instance of a command that isn't following that is a bug.
Which of course leaves room for improvement in documentation and how
we organize the implementation (as Peff discussed in ), but isn't
it nice to already have something in place that doesn't require
inventing a new syntax?