On 18. aug. 2010, at 17.50, Thomas Berg wrote: > Hi, > > On Wed, 2010-08-18 at 15:18 +0200, Eyvind Bernhardsen wrote: >> Git _is_ giving you a real pristine copy, it's just informing you that your repository is not consistent with the attributes you have set. > > Marking the files as modified is sometimes a very user-unfriendly way > of informing the user, at least if just want to work with something > unrelated, and not actually fix those issues. Maybe there is a better > way? There may be, but I'm not sure it would be worth the effort. The reason I started working on CRLF normalization in the first place was because I got tired of seeing spuriously modified files everywhere when using core.autocrlf, so I know how annoying it is. The difference now is that only people using "mis-attributed" repositories are annoyed, instead of anyone who uses core.autocrlf, and as I wrote elsewhere, I don't expect there to be many repositories where this is a problem. To be clear: triggering the problem not only requires that a crlf attribute is set to something other than "false", but also that the corresponding file actually contains CRs. - 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