On Wed, Jul 21, 2010 at 5:35 PM, John Dlugosz <JDlugosz@xxxxxxxxxxxxxxxx> wrote: >> > Running git config --list shows nothing that would suggest any such >> setting. >> >> Try 'git config --global --list' > > I thought that --list tells me the sum result of all the settings in force; i.e. the final result that should be used here and now. Sadly not. >> Try 'git config --global --list' > > I get: fatal: $HOME not set Yow, that's kind of bad news. It implies that if you run git from one shell, it will be able to find your global .gitconfig (and thus use autocrlf), but if you run it from a different kind of shell, it won't. This could be the root of your problem. One "solution" would be to change git to always die immediately if $HOME isn't set. > So, assuming it's been that way (the file is dated March), what's the repository "really" > doing? When things started acting funny, my co-worker found this setting and removed > it from his. If that's not it, I can only wonder why it started showing all-lines-changed ? I don't know. One thing I do know is that changing the autocrlf setting on an active repository makes git go bonkers and there's no (as far as I know) well-documented way to un-bonkers it other than to just check out everything again. If your problem really is that the ~/.gitconfig comes and goes (as far as git is concerned), it could certainly have caused this problem. Have fun, Avery -- 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