o Santilli
> Sent: Tuesday, August 29, 2017 4:10 PM
> To: GEOS Development List <geos-devel@lists.osgeo.org>
> Subject: Re: [geos-devel] Accompanying .editorconfig with .gitattributes?
>
> On Tue, Aug 29, 2017 at 05:56:17PM +0200, Mateusz Loskot wrote:
> > Hi,
> >
&g
-devel] Accompanying .editorconfig with .gitattributes?
On Tue, Aug 29, 2017 at 05:56:17PM +0200, Mateusz Loskot wrote:
> Hi,
>
> Since .editorconfig now forces LF/CRLF per file type in the codebase,
> wouldn't it be a good idea to add .gitattributes with explicit eol=
> specificat
On 08/29/2017 05:56 PM, Mateusz Loskot wrote:
> Since .editorconfig now forces LF/CRLF per file type in the codebase,
> wouldn't it be a good idea to add .gitattributes with explicit
> eol= specification per file type too?
>
> This would ensure git checkout/commit does not re-convert line endings
On Tue, Aug 29, 2017 at 05:56:17PM +0200, Mateusz Loskot wrote:
> Hi,
>
> Since .editorconfig now forces LF/CRLF per file type in the codebase,
> wouldn't it be a good idea to add .gitattributes with explicit
> eol= specification per file type too?
>
> This would ensure git checkout/commit does
Subject: [geos-devel] Accompanying .editorconfig with .gitattributes?
Hi,
Since .editorconfig now forces LF/CRLF per file type in the codebase, wouldn't
it be a good idea to add .gitattributes with explicit eol= specification per
file type too?
This would ensure git checkout/commit does not re
Hi,
Since .editorconfig now forces LF/CRLF per file type in the codebase,
wouldn't it be a good idea to add .gitattributes with explicit
eol= specification per file type too?
This would ensure git checkout/commit does not re-convert line endings
differently than as expected by .editorconfig.
