From: Junio C Hamano <gitster@pobox.com>
Date: Tue, 03 Jul 2018 16:01:05 GMT
Subject: Re: Use of new .gitattributes working-tree-encoding attribute across different platform types
Message-ID: <xmqqsh50s3zy.fsf@gitster-ct.c.googlers.com>
In-Reply-To: <20180702181742.GA12208@sigill.intra.peff.net>

Jeff King <peff@peff.net> writes:

> One thing I almost did in the example I gave above was to literally call
> the encoding name by a "real" one. I.e.:
>
>   echo '*.txt working-tree-encoding=iso-8859-1' >.gitattributes
>   git config encoding.iso-8859-1.replace latin1
>
> or something. But I wondered if it was a little crazy as a practice,
> since mapping "iso-8859-1" to "utf-8" is probably going to lead to
> headaches.
>
> But your example above of semantically equivalent variants with
> different spellings would be a good use of that trick.

Yeah, I think the above looks quite sensible.