Am 15.04.2014 um 23:23 schrieb Junio C Hamano <gits...@pobox.com>: > Brandon McCaig <bamcc...@gmail.com> writes: > >> That is for your benefit, and for easily sharing that configuration >> with collaborators. Git only cares that the file exists in your >> working tree at run-time. > > It is a lot more than "for sharing". If you made .gitignore only > effective after it gets committed, you cannot test your updated > version of .gitignore is correct before committing the change.
Ok, I can follow that logic for .gitignore, but I was talking about .gitattributes and I always thought that .gitattributes as belonging to the repository, since it affects a) how files are checked out and b) how they are stored inside the repository. If committing .gitattributes were only for sharing convenience, git couldn’t decide whether to convert line endings when checking out a file. The same behavior doesn’t apply to .gitignore, because git will checkout a file that was added even though it matches an ignore pattern in .gitignore. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
