Hi, I'm sorry I've taken so long to respond. On 25. mai 2010, at 10.27, Anthony Youngman wrote: > Just a suggestion ... > For core.autocrlf (or somewhere else more appropriate) could we add to > false and true the option "force"? > > Bearing in mind "force" is always considered "a bit dangerous", that > merely means "I don't care if it has crlf in the repository, change all > commits to lf" (and checkouts to crlf if appropriate). > > Yep, things are likely to break, but I'm thinking this is the sort of > situation where a lead dev could say to themselves "I know what I'm > doing, we need to clean up, and if I set that as my options, then I know > I can fix any resulting mess". If I understand you correctly, putting "* text=auto" in .gitattributes would do what you want, with the added benefit that you document the decision to normalize inside the repository. If you don't think that's a benefit, you can put "* text=auto" in .git/info/attributes for the same normalizing effect. -- Eyvind -- 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