Re: Is the "text" attribute meant *only* to specify end-of-line normalization behavior, or does it have broader implications?
- From
Junio C Hamano <gitster@pobox.com>
- Date
- Mar 30, 2012, 18:22 UTC
- Message-ID
- <7v62dmlzjl.fsf@alter.siamese.dyndns.org>
- In-Reply-To
- <CANSc5vGaodyv4H5qp2ZkjY7q6ot7_JG0jdvNDFRBFW1+p7v4sw@mail.gmail.com>
Chris Harris <ryguasu@gmail.com> writes:
Show 8 quoted lines
> A related point of confusion: I've noticed that, if you start with a > question along the lines of "how can I explicitly tell git that a file > is binary", then the web currently gives a slightly confusing array of > answers. For example: >... > It makes me wonder if the documentation could be improved a little on > this count, though I don't yet feel solid enough in my understanding > to propose a particular patch.
If you only read your analysis on gitattributes documentation, it would be clear that text/-text does not have much to do with binaryness, and it also gives an authoritative advice "binary".
We do not have direct control over third-party sites that give incorrect information, so people need to bug them as they find mistakes. I think ProGit actively accepts patches; I do not know about others.
Thanks.