Re: [PATCH v7 0/7] convert: add support for different encodings
- From
Junio C Hamano <gitster@pobox.com>
- Date
- Feb 16, 2018, 19:41 UTC
- Message-ID
- <xmqqk1vc67tb.fsf@gitster-ct.c.googlers.com>
- In-Reply-To
- <20180216192727.GA23249@sigill.intra.peff.net>
Jeff King <peff@peff.net> writes:
> In which case yeah, I could see choosing an in-repo encoding to possibly > be useful (but it also seems like a feature that could easily be tacked > on later if somebody cares).
Yes, I think we are on the same page---in-repo-encoding that is a natural counterpart to w-t-e attribute can be added later if/when somebody finds it useful, and it is perfectly OK to declare that we cater only to UTF-8 users until that happens.