On Mon, Jul 02, 2018 at 04:09:32PM +0200, Lars Schneider wrote:
> Brian had a good argument [1] for an even more flexible system
> proposed by Peff:
>
>
> 1) We allow users to define custom encoding mappings in their Git config.
> Example:
>
> git config --global core.encoding.myenc UTF-16
I think this should be encoding.myenc.something. In Git's config format,
only the subsection names (the middle of a three-dot name) are
unconstrained. So even if encoding.myenc only ever has one key
("replace" or "useInstead" or whatever you want to call it), there's
value in organizing the namespace that way.
And as a bonus, it leaves room for extending the feature later if we do
need more keys.
-Peff
