Mailing-List: contact dev-help@groovy.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@groovy.apache.org
Date: Fri, 15 Jan 2016 13:41:31 -0800
From: Konstantin Boudnik <cos@apache.org>
To: dev@groovy.apache.org
Subject: Re: Normalize line endings?
Message-ID: <20160115214131.GS22241@tpx>
References: <5699410F.607@gmx.net>
 <1452885611.2939.122.camel@winder.org.uk>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;
	protocol="application/pgp-signature"; boundary="qMOP63lkUNNMsXoM"
Content-Disposition: inline
In-Reply-To: <1452885611.2939.122.camel@winder.org.uk>
User-Agent: Mutt/1.5.21 (2010-09-15)


--qMOP63lkUNNMsXoM
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Fri, Jan 15, 2016 at 07:20PM, Russel Winder wrote:
> On Fri, 2016-01-15 at 19:57 +0100, Pascal Schumacher wrote:
> > Hello everybody,
> >=20
> > should the line endings of all source files in git be normalized to
> > "\n"?
> >=20
> > see the discussion at https://github.com/apache/groovy/pull/236
> >=20
>=20
> The answer to this has always been yes. Git strategy has always been
> that Windows people should use the mapping capability in Git. Sadly not
> everyone has always heeded this and there are large number of \r\n line
> endings committed into the repository. This is wrong. No ifs, no buts.

I'd say the issue is even deeper: sadly some are still using systems with
\r\n line endings ;)

Cos

--qMOP63lkUNNMsXoM
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iF4EAREIAAYFAlaZZ4sACgkQenyFlstYjhLA4AEAk+08/TfVYfZCcG9jg/Iy60P3
jtBEu4PUmkXPEgVtej0BAJrb5KQOUUC+YRtT8VwcRPDlOVqnmxwdBUiBgVUKDDne
=6ega
-----END PGP SIGNATURE-----

--qMOP63lkUNNMsXoM--