What are the ways CRLF files can make it into the repository?

Joshua Jensen· Sep 21, 2012, 19:02 UTC · lore

Hi.

We've been running with core.autocrlf = input (some people with core.autocrlf = true). However, there are some text files in the repository that are CRLF, and I am at a loss to explain how they go here.

We understand that if core.autocrlf=false, this could happen. While I admit there is a remote possibility this did occur, I'm not convinced our people were smart enough with Git 1.5 years ago to make this configuration change.

There are no .gitattributes settings for these source code files.

Are there other ways CRLF files could sneak into the repository?

Thanks.

Josh

Konstantin Khomoutov· Sep 22, 2012, 12:08 UTC · re: Joshua Jensen · lore

Re: What are the ways CRLF files can make it into the repository?

On Fri, Sep 21, 2012 at 01:02:11PM -0600, Joshua Jensen wrote:

Show 13 quoted lines

> We've been running with core.autocrlf = input (some people with
> core.autocrlf = true).  However, there are some text files in the
> repository that are CRLF, and I am at a loss to explain how they go
> here.
> 
> We understand that if core.autocrlf=false, this could happen.  While
> I admit there is a remote possibility this did occur, I'm not
> convinced our people were smart enough with Git 1.5 years ago to
> make this configuration change.
> 
> There are no .gitattributes settings for these source code files.
> 
> Are there other ways CRLF files could sneak into the repository?

Is there any chance Git considered them binary for some reason and hence did not apply its EOL-conversion logic at all?