On 18/10/17 15:15, Mark Rotteveel wrote:
Given the normalization done during conversion, that should not be a problem (unless a new file extension is introduced that isn't considered a text file by the configuration of the conversion).
The thing I mentioned with autocrlf is the old way of doing things, up to Git 1.6 I think. From then on, .gitattributes is the way to go.
However, if a new file type appears, Git will determine whether it is a text file by checking to see if it fails the tests for binary files.
There's a good explanation of why it might be best to have both settings at http://adaptivepatchwork.com/2012/03/01/mind-the-end-of-your-line/.
Cheers, Norm. -- Norman Dunbar Dunbar IT Consultants Ltd Registered address: 27a Lidget Hill Pudsey West Yorkshire United Kingdom LS28 7LG Company Number: 05132767 ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Firebird-docs mailing list Firebird-docs@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/firebird-docs
