Dragan Simic <dsimic@xxxxxxxxxxx> writes: > Though, further investigation shows that setting a configuration value, > by invoking git-config(1), converts value-internal tabs into "\t" escape > sequences, which the value-parsing logic doesn't "squash" into spaces. Correct. It would have been nicer to just quote values that had whitespaces in them, but replacing HT to SP while turning HT that comes from our tool into "\t" would still let the value round-trip, while breaking anything written manually in editors. If you stay within Git without using any editor, what ebdaae37 (config: Keep inner whitespace verbatim, 2009-07-30) left us is at least internally consistent. > I'd be happy to include the bugfix into this series, if my > above-mentioned > fears prove to be unnecessary. Documenting status quo is a good place to stop for now. I do not know if it is a good idea to add too many tests to etch the current behaviour that we know is wrong and we'll need to update when we fix the bug, though. Thanks.
