Good stuff Tim!

One thing I do differently, which some people might find useful to know, is set the core.autocrlf setting local to the repository, rather than globally. You do this by using the same git config command, just without the --global switch. What this does is remove the need to re-clone after changing the setting. Doing another git status after changing the setting locally should immediately reflect the config change and not show any changes.

In the msysgit installer, you're presented with a radio list for Windows line endings, Unix line endings, or "Don't screw with line endings" (or something to that effect).  That, or editing %PROGRAM FILES%\Git\etc\gitconfig is how you can change the global setting (the one that shows up first in your git config -l).

With .NET code and designer-generated files, I've just switched entirely to autocrlf = false, as different tools will intermix and modify your line endings.  It'd be nice to have them all the same, but then you get into commits whose sole purpose was to fix the line endings in a resource file or designer file, and that's just not worth it.

One more thing - don't forget it's autocrlf and not autoclrf. I had a few interesting moments today before I had a duh moment. :D

This post was mentioned on Twitter by devlicious: New Blog Post I Just Cloned, Why Did Git Change My Files?: Being new to Git I got thrown off a few weeks ago when c... http://bit.ly/4wDY1I