Re: [PATCH] optionally disable gitattributes

2016-01-27 Thread Clemens Buchacher
On Wed, Jan 27, 2016 at 04:04:39PM +0100, Torsten Bögershausen wrote: > > It feels like a workaround for something that could be fixable, or is already > ongoing. > Before going into more details, > could you tell us which attributes you are typically using (when having this > problems) ? > Is it

Re: [PATCH] optionally disable gitattributes

2016-01-27 Thread Torsten Bögershausen
On 27.01.16 12:59, Junio C Hamano wrote: > Clemens Buchacher writes: > >> If committed files are not normalized, adding gitattributes has the >> side effect that such files are shown as modified, even though they >> were not actually modified by the user, and the work tree matches >> the committe

Re: [PATCH] optionally disable gitattributes

2016-01-27 Thread Junio C Hamano
Clemens Buchacher writes: > If committed files are not normalized, adding gitattributes has the > side effect that such files are shown as modified, even though they > were not actually modified by the user, and the work tree matches > the committed file. This is because with gitattributes, the f

[PATCH] optionally disable gitattributes

2016-01-27 Thread Clemens Buchacher
If committed files are not normalized, adding gitattributes has the side effect that such files are shown as modified, even though they were not actually modified by the user, and the work tree matches the committed file. This is because with gitattributes, the file is modified on the fly when git