Re: [PATCH v1] convert: add support for 'encoding' attribute

From: Junio C Hamano <gitster@pobox.com>
Date: Dec 13, 2017, 18:11 UTC
Message-ID: <xmqqzi6mwlai.fsf@gitster.mtv.corp.google.com>
In-Reply-To: <D2973852-BDF4-4251-8DE3-CE6AAD303A5F@gmail.com>

Lars Schneider <larsxschneider@gmail.com> writes:

Show 5 quoted lines

> ... In a perfect world I think I would store
> the encoding of a file in the tree object. I didn't pursue that solution
> as this would change the Git data model which would open a can of worms
> for a problem that not that many people have (almost everyone is on
> UTF-8 anyways).

Having that "encoding" trailt recorded in the tree that contains the blob would mean that the same blob can be recorded with one "encoding" trait in a tree, and in a different tree it can be recorded with a different "encoding" trait. I doubt it really makes sense.