Re: Consequences of CRLF in index?

From: Johannes Schindelin <johannes.schindelin@gmx.de>
Date: Oct 27, 2017, 15:18 UTC
Message-ID: <alpine.DEB.2.21.1.1710271716330.6482@virtualbox>
In-Reply-To: <30ED36AB-FAB1-4635-94AF-FCEC6F02CE01@gmail.com>

Hi Lars,

On Thu, 26 Oct 2017, Lars Schneider wrote:

Show 12 quoted lines

> > On 26 Oct 2017, at 09:09, Johannes Sixt <j6t@kdbg.org> wrote:
> > 
> > Am 25.10.2017 um 14:19 schrieb Johannes Schindelin:
> >> I envy you for the blessing of such a clean C++ source that you do not
> >> have any, say, Unix shell script in it. Try this, and weep:
> >> 	$ printf 'echo \\\r\n\t123\r\n' >a1
> >> 	$ sh a1
> >> 	a1: 2: a1: 123: not found
> > 
> > I was bitten by that, too. For this reason, I ensure that shell
> > scripts and Makefiles begin their life on Linux. Fortunately, modern
> > editors on Windows, includ^Wand vi, do not force CRLF line breaks, and

                        ^^^^^^^^^^^^^^

This put a well-needed smile on my face. Thanks.

Show 6 quoted lines

> > such files can be edited on Windows, too.
> 
> Wouldn't this kind of .gitattributes setup solve the problem?
> 
> *     -text
> *.sh   text eol=lf

If you look at the commit I mentioned, you will see examples where it breaks down: when using Unix shell scripts *without* .sh file extension. Most notable offender: GIT-VERSION-GEN.

Ciao, Dscho