Greetings, It seems that, for example, glob pattern *.s matches files with .sh extension at least with checkout and reset --hard but git status thinks otherwise: mkdir test cd test git init echo -e "*.sh -crlf\n*.s crlf" > .gitattributes echo -e "foobar\nfoobar\nfoobar" > kala.s echo -e "foobar\nfoobar\nfoobar" > kala.sh git add .gitattributes kala.s kala.sh git commit -m "Foo." cd .. git clone -n test test2 cd test2 git config core.autocrlf true git checkout git status # On branch master # Changed but not updated: # (use "git add <file>..." to update what will be committed) # (use "git checkout -- <file>..." to discard changes in working # directory) # # modified: kala.sh # no changes added to commit (use "git add" and/or "git commit -a") file kala.s kala.sh kala.s: ASCII text, with CRLF line terminators kala.sh: ASCII text, with CRLF line terminators Tested in Linux with git 1.6.0.3.535.g933bb (master as of this writing) but also witnessed in Windows and with slightly older git versions. This makes git use in a Windows environment pretty much impossible if you don't want to / can't rely on git guessing "text" vs. "binary" files correctly so I hope a solution is found soon. It would also be good to document what kind of glob patterns git actually supports. I made the assumption that at least on Linux it supports whatever glob(7) says but even if that assumption is correct (which it may not be, of course) for example Windows users may not realize to look for such a manual page. -- Hannu -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
