Re: [PATCH] Documentation/i18n.txt: clarify character encoding support

2015-06-17 Thread Junio C Hamano
Karsten Blees karsten.bl...@gmail.com writes: I do not think the removal of the text makes much sense here unless you add the equivalent to the new text below. - The contents of the blob objects are uninterpreted sequences of bytes. There is no encoding translation at the core

Re: [PATCH] Documentation/i18n.txt: clarify character encoding support

2015-06-15 Thread Karsten Blees
Am 15.06.2015 um 02:12 schrieb Junio C Hamano: Karsten Blees karsten.bl...@gmail.com writes: diff --git a/Documentation/i18n.txt b/Documentation/i18n.txt index e9a1d5d..e5f6233 100644 --- a/Documentation/i18n.txt +++ b/Documentation/i18n.txt @@ -1,18 +1,28 @@ -At the core level, Git is

[PATCH] Documentation/i18n.txt: clarify character encoding support

2015-06-13 Thread Karsten Blees
As a distributed VCS, git should better define the encodings of its core textual data structures, in particular those that are part of the network protocol. That git is encoding agnostic is only really true for blob objects. E.g. the 'non-NUL bytes' requirement of tree and commit objects excludes