Re: .gittattributes handling has deficiencies

From: Steffen Prohaska <prohaska@zib.de>
Date: Oct 21, 2007, 10:27 UTC
Message-ID: <B61AE1A9-E983-4ACE-BF71-8FDC113A4F34@zib.de>
In-Reply-To: <Pine.LNX.4.64.0710210204580.4818@asgard>

On Oct 21, 2007, at 11:19 AM, david@lang.hm wrote:

Show 9 quoted lines

>> But this is really hard to solve. We would need to compare
>> attributes before and after for _all_ files that have attributes
>> in one of the two commits and check if they changed. If so, we
>> need to do a fresh checkout according to the new attributes.
>
> if you know that you will get the new .gitattributes if it changes,  
> setup a post-checkout hook to checkout everything if it has  
> changed. it's far from ideal, but it should be a good, safe, first  
> approximation.

That's not good enough. I'll stop using .gitattributes. I need to teach >40 devs how to use git on Windows. I only use features that work flawlessly. .gitattributes doesn't. It bit me twice now.

Luckily, core.autocrlf works if you set it before the first checkout and never change it. This seems sufficient for me if all files that have mixed line endings are fixed right away.

	Steffen