Re: [PATCH v9 5/8] convert: add 'working-tree-encoding' attribute

2018-03-06 Thread Eric Sunshine
On Tue, Mar 6, 2018 at 5:13 PM, Lars Schneider wrote: >> On 06 Mar 2018, at 21:42, Eric Sunshine wrote: >> On Sun, Mar 4, 2018 at 3:14 PM, wrote: >>> + return xstrdup_toupper(value); >> >> xstrdup_toupper()

Re: [PATCH v9 5/8] convert: add 'working-tree-encoding' attribute

2018-03-06 Thread Lars Schneider
> On 06 Mar 2018, at 21:42, Eric Sunshine wrote: > > On Sun, Mar 4, 2018 at 3:14 PM, wrote: >> Git recognizes files encoded with ASCII or one of its supersets (e.g. >> UTF-8 or ISO-8859-1) as text files. All other encodings are usually >>

Re: [PATCH v9 5/8] convert: add 'working-tree-encoding' attribute

2018-03-06 Thread Eric Sunshine
On Sun, Mar 4, 2018 at 3:14 PM, wrote: > Git recognizes files encoded with ASCII or one of its supersets (e.g. > UTF-8 or ISO-8859-1) as text files. All other encodings are usually > interpreted as binary and consequently built-in Git text processing > tools (e.g.

[PATCH v9 5/8] convert: add 'working-tree-encoding' attribute

2018-03-04 Thread lars . schneider
From: Lars Schneider Git recognizes files encoded with ASCII or one of its supersets (e.g. UTF-8 or ISO-8859-1) as text files. All other encodings are usually interpreted as binary and consequently built-in Git text processing tools (e.g. 'git diff') as well as most Git