----- Original Message ----- 
  From: Craig Street 
  To: Git for human beings 
  Cc: craig.str...@gmail.com 
  Sent: Wednesday, April 06, 2016 2:41 PM
  Subject: Re: [git-users] GIT Line Endings

    Many thanks

  for some reason I thought the core.autocrlf worked both ways (ie also checked 
out using LF only on *nix).

  Forcing a checkout made no difference, however given your comments I changed 
.gitattributes to

  *.sh eol=lf

  ie (removed text), which had the desired effect.

  Its not clear to me how or if 'text' and 'eol' should be used together. The 
description at https://git-scm.com/docs/gitattributes suggest they can be used 
together, although the examples show them used separately.

  Looks like GIT had assumed the *.sh file was not a text file in this instance.


There has been a recent patch series looking into some of the LF - CRLF 
checkout issues [1], though it may not address your direct issues.

The different communities don't exactly agree what 'normalisation' should mean. 
The general important point being that what is in the commit (in the 
repository) stays in the commit. If you want something different (in the 
repository) it's a new commit. 


[1] http://article.gmane.org/gmane.comp.version-control.git/290554 and 
subsequent versions e.g. 

You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to git-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to