Ramsay Jones writes:
>> +Show line endings ("eolinfo") and the text/eol attributes
>> ("texteolattr") of
>> files.
>> +"eolinfo" is the file content identification used by Git when
>> +the "text" attribute is "auto", or core.autocrlf != false.
>> ++
>> +"eolinfo" is either "" (when t
Torsten Bögershausen writes:
> Add test cases in t0027, thanks to Junio C Hamano for the optimized
> grep-less sed expression.
Please drop this part; it is embarrassing.
You wouldn't thank all the mentors you have ever had from whom you
learned programming in your log messages, either ;-)
--
To
>> "binary" binary file
>> "text-no-eol" text file without any EOL
>> "text-lf" text file with LF
>> "text-crlf"text file with CRLF
>> "text-crlf-lf" text file with mixed line endings.
> If you prefer to have 'text' in there somewhere, how about:
>
>binary, text-none, text-lf,
On 30/12/15 12:57, Torsten Bögershausen wrote:
> When working in a cross-platform environment, a user wants to
> check if text files are stored normalized in the repository and if
> .gitattributes are set appropriately.
>
> Make it possible to let Git show the line endings in the index and
> in
When working in a cross-platform environment, a user wants to
check if text files are stored normalized in the repository and if
.gitattributes are set appropriately.
Make it possible to let Git show the line endings in the index and
in the working tree and the effective text/eol attributes.
The
5 matches
Mail list logo
