1

I am in charge of system engineer at Japanese company.
We are programmed POS by VB6 and our source managed by Git.

Currently we notice ".bas", ".frm" extensions are not targeted autocrlf.
We checked ".gitignore", "gitignore_global". But we did not set these extensions.

I want to know the reason why extensions was not changed.

VonC
  • 1,262,500
  • 529
  • 4,410
  • 5,250
Takeru
  • 11
  • 2
  • It seems that git did not recognize files with ,bas and .frm extension as a text file. – gzh Aug 23 '17 at 03:13
  • Add a `.gitattributes` file and specify those files are text files. – Jeff Mercado Aug 23 '17 at 03:22
  • you mean when you check the `git status` it doesn't show `.bas` or `.frm` files got change ? – ntshetty Aug 23 '17 at 03:22
  • You can refer to https://git-scm.com/docs/gitattributes on how to tell git handle a file as text file. – gzh Aug 23 '17 at 03:24
  • so sorry. i mean that currently our autocrlf status is true. so if we commit and push to git, the sources will change crlf to lf. but ".bas", ".frm" files did not change. if we need to automatically change, we must add ".gitattributes" ? – Takeru Aug 23 '17 at 03:58

1 Answers1

0

but ".bas", ".frm" files did not change

That might be because of an existing .gitattributes which would instruct the file eol style differently.

*.bas       text eol=lf
*.frm       text eol=lf
VonC
  • 1,262,500
  • 529
  • 4,410
  • 5,250
  • Thank you for your answer. We did also check .gitattributes which is existing or not. But the file is nothing... Do you know anything file which is relation to change crlf to lf? – Takeru Aug 23 '17 at 06:26
  • @Takeru if there is no .gitattributes, then you can follow https://stackoverflow.com/a/13154031/6309 or https://stackoverflow.com/a/33424884/6309 – VonC Aug 23 '17 at 06:42
  • Thank you for your cooperation. I will follow and continue to search this problem. – Takeru Aug 23 '17 at 07:00