On Tue, Feb 27, 2018 at 6:16 AM, Lars Schneider
wrote:
>> On 25 Feb 2018, at 08:15, Eric Sunshine wrote:
>> On Sat, Feb 24, 2018 at 11:27 AM, wrote:
>> The above paragraph is giving an example of the scenario described in
>> the paragraph above it. It might, therefore, be clearer to start this
> On 25 Feb 2018, at 08:15, Eric Sunshine wrote:
>
> On Sat, Feb 24, 2018 at 11:27 AM, 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 t
On Sat, Feb 24, 2018 at 11:27 AM, 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. 'git diff') as well as most Gi
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 web front ends do not
visu
4 matches
Mail list logo
