Jeff King <p...@peff.net> writes: > I half-agree. Config that causes unpredictable behavior can break > somebody else's script that you are running. If you say "oh, I guess I > shouldn't set that config" and move on with your life, then the config > hasn't really hurt anybody. If you complain to the script author that > their script is broken, and insist that they pass the --no-foo option, > then the script writer does not care much whether it was a config option > or a change of default.
Hmph, I never considered that POV but you are right. I am not sure if that argues that we have to be even more careful not to add non-essential configuration variable, or that we can afford to be much less careful when changing the default, though. A little bit of both, I guess. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
