> -----Original Message----- > From: git-owner@xxxxxxxxxxxxxxx [mailto:git-owner@xxxxxxxxxxxxxxx] On > Behalf Of Jeff King > Sent: Monday, November 03, 2008 11:15 PM > To: Hannu Koivisto > Cc: git@xxxxxxxxxxxxxxx > Subject: Re: CRLF support bugs (was: Re: .gitattributes glob > matchingbroken) > > On Mon, Nov 03, 2008 at 05:05:24PM +0200, Hannu Koivisto wrote: > <snip> > > I think CRLF conversion support should have some attribute (be it > > .gitattributes attribute or something else) that is somehow > > inherited from the parent repository. It would basically say that > > "you should use platform's native line end type for text files with > > this repository and its children". To go with that, one would > > maybe have a configuration option to tell what that platform > > default line end type is (just in case someone wants to pretend > > Cygwin is Unix or something like that). > > I think others have complained before about something like this, in > that > it really is a _local_ decision and not a _project_ decision to make. I > am fortunate enough to work exclusively on platforms with sane line > endings, so I don't know what is normal. >From my point of view, the factoid that a particular file should be subjected to having its line endings munged is a _project_ decision. Whether or not to munge them on any given platform is a _local_ decision. I work on various UNIXes, Linux, Windows, z/OS, etc, etc, and I want the tool to just do the right thing so that I don't have to think about it on a daily basis. My $0.02.... -Kelly > > But if you really wanted to do such a thing for some set of corporate > users, maybe it would make sense to have a "clone" hook that runs after > init and can set up any relevant config (e.g., by copying certain > config > values from the parent repo). > > -Peff ��.n��������+%������w��{.n��������n�r������&��z�ޗ�zf���h���~����������_��+v���)ߣ�m
