On 2017-11-14 13:31, Ashish Negi wrote: > Hello > > I have a cross platform project. I have a utf-16 file in it. > I changed its encoding to urf-8 and committed. When i pulled the file > in Linux, it shows that file is modified. This means that the commit > which changed the encoding does not convert crlf to lf, when new > format is text based (utf-8). > > Steps to reproduce: > > In windows : > > Change encoding of file from utf-16 to utf-8. > Commit the change. > > In linux: > > Pull your branch. > You will see the issue of file being shown as modified even though > you have not used it. > > > If i change the file encoding in linux and commit. Then if i do git > pull in windows, i don't see the issue. > In linux, during committing i get warning : warning: CRLF will be > replaced by LF in …file_name.. > > Here are my configuration : > > >> git config --global --get core.autocrlf > > false > > >> git config --get core.autocrlf > > false > > > >> cat E:\work\WindowsFabric\.gitattributes > > > # Set the default behavior, in case people don't have core.autocrlf set. > > * text=auto > *.vcxproj eol=crlf > *.sh eol=lf > > # Denote all files that are truly binary and should not be modified. > *.exe binary > *.dll binary > *.pdb binary > *.ico binary > *.png binary > *.jpg binary > > >> git --version > git version 2.14.2.windows.2 > > > I played around with core.autocrlf values like true and native, but > that didn't help. > > The behavior is inconsistent across platforms, and windows version is > giving me problem. > > Can someone suggest right settings for this ? Or is this a bug in Git. >
I don't think it is a bug :-) What does git ls-files --eol …file_name give you under Windows ?
