Re: [PATCH] Respect crlf attribute even if core.autocrlf has not been set

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,

On Wed, 23 Jul 2008, Junio C Hamano wrote:

> Johannes Schindelin <Johannes.Schindelin@xxxxxx> writes:
> 
> > On Wed, 23 Jul 2008, Junio C Hamano wrote:
> > ...
> >> If you are on a sane system, you do not even want to pay the price of 
> >> conversion.  Only people on systems with CRLF line endings should pay 
> >> the price (because your aim is to convert on such systems).  Are we 
> >> throwing that out of the window when the project decides to use 
> >> gitattributes?
> >
> > Well, if you do not want that, why do you set crlf in the 
> > gitattributes to begin with?
> 
> It is not _me_ but the project upstream that needs to interact also with 
> Windows people who manages gitattributes.  And me personally knows my 
> editors are not helpful to add CR at the end of lines, so I do not need 
> the conversion.

I know you do.  And I know those users don't.  They do not even know that 
they should set autocrlf = input in their cygwin Git.

Or at least, now they do.  After a few hundred commits that have been 
published _after_ their broken checkins.

Sigh,
Dscho

--
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

[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]

  Powered by Linux