On Fri, Sep 21, 2012 at 01:02:11PM -0600, Joshua Jensen wrote: > 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?
-- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
