Re: Is the "text" attribute meant *only* to specify end-of-line normalization behavior, or does it have broader implications?

[Johannes Sixt <j.sixt@viscovery.net>]

Am 3/30/2012 4:19, schrieb Chris Harris:
> I'm starting a new repository for a Windows-only project where I don't
> think I want git to do any end-of-line normalization on my text files.
> (I'm totally happy to have CRLFs both in the repo and in all the
> working copies.)

The question is rather: Are you happy if someone commits a file that does
*not* have CRLF, but only LF?

Because if you don't care, you are better off setting no attributes and no
core.autocrlf and no core.eol at all. The git will take the file
unmodified. If someone's editor changes the eol style of a file, it will
be noticed because the diff will show that the entire file has changed.
Your team mates should better have enough discipline not to ignore such a
hint that something's gone awry, of course.

> Unless you think that end-of-line normalization is
> always vital, let's try to presume I've made the right choice about
> this.

It's your code, you are to judge what is best for you. IOW, I don't think
that eol normalization is "always vital", and you are right. :-)

(I didn't answer the question in the subject of your message, and I can't;
I don't use the text attribute nor eol normalization, even though I work
on Windows quite a lot.)

-- Hannes