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? On Wed, Aug 18, 2010 at 4:14 PM, Will Palmer <wmpalmer@xxxxxxxxx> wrote: > "pristine" to me means "no changes". If there is an inconsistency which > git doesn't like, git should complain about that, refuse to checkout, > declare "broken repository! Oh no!" and refuse all operations, etc. It > git can determine that it is unable to act in a sane manner, I don't > want git to just go ahead making wild guesses. > [snip] > Just to re-state: This is not "my repository". That is, I don't consider > it to be. So I would prefer only solutions which involve editing > something unversioned, such as .git/config, rather than making random > patches which feel very much like work-arounds to a git problem. Such a solution exists, you can create a file .git/info/attributes, which will override the faulty .gitattributes file in the repository [1]. Then you could make git treat all files as binary files, making no conversions. Using this unversioned file also enables you to jump back in history, rebase etc. without problems. Hope this helps, Thomas [1] http://www.kernel.org/pub/software/scm/git/docs/gitattributes.html -- 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