On Fri, Feb 26, 2016 at 11:34 AM, Junio C Hamano <gits...@pobox.com> wrote: > > Of course, the code in the configuration subsystem for updated > version of Git needs to become aware of the new syntax, and those > that deal with the multi-value variables need custom code, which is > similar to the way you special cased an empty value in the above > patch, so I am not sure how much this would help. >
For most cases, I think the previous approach of setting to empty string makes sense and is more easilly intuitive, but would only work for those values which the empty string has no valid meaning. I would think either approach here is fine, and i think *most* cases of multivariable configuration don't need to be cleared from within a configuration file but only on the command line would be acceptable. If we go this route I would prefer "-c !<config>" vs "-c <namespace>.!<config>" Thanks, Jake -- 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
