On 31.10.2015 11:25, Matthieu Moy wrote:
>> ca:text-no-eol wt:text-no-eol t/t5100/empty
>> ca:binarywt:binaryt/test-binary-2.png
>> ca:text-lf wt:text-lf t/t5100/rfc2047-info-0007
>> ca:text-lf wt:text-crlf doit.bat
>> ca:text-crlf-lf wt:text-crlf-lf
Matthieu Moy writes:
> Torsten Bögershausen writes:
>
>> ca:text-no-eol wt:text-no-eol t/t5100/empty
>> ca:binarywt:binaryt/test-binary-2.png
>> ca:text-lf wt:text-lf t/t5100/rfc2047-info-0007
>> ca:text-lf
Sebastian Schuberth writes:
> However, the commit message says "to check if text files are stored
> normalized in the *repository*", yet the output refers to the index /
> cache. Is there a (potential) difference between line endings in the
> index and repo?
There is when
Junio C Hamano writes:
> i/ and w/ have been used to denote the "i"ndex and "w"orktree
> versions for the past 7 years with diff.mnemonicprefix option,
> which you may want to match.
Indeed.
--
Matthieu Moy
http://www-verimag.imag.fr/~moy/
--
To unsubscribe from this list:
On Sun, Nov 1, 2015 at 7:40 PM, Matthieu Moy
wrote:
>> Any I find it a bit confusing to refer to the index where, as e.g. for
>> a freshly cloned repo the index should be empty,
>
> No it is not. The index is a complete snapshot of your working tree.
> When you have
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 cache and
in the working tree.
Files which are treated as binary by Git,
Torsten Bögershausen writes:
> ca:text-no-eol wt:text-no-eol t/t5100/empty
> ca:binarywt:binaryt/test-binary-2.png
> ca:text-lf wt:text-lf t/t5100/rfc2047-info-0007
> ca:text-lf wt:text-crlf doit.bat
> ca:text-crlf-lf wt:text-crlf-lf
7 matches
Mail list logo