Poco is using the .gitattributes file instead, which doesn't depend on client settings,

On Wed, Nov 7, 2012 at 11:31 AM, Andre Haupt <andre@bitwigglers.org> wrote:
Hi all,

On Wed, Nov 07, 2012 at 11:07:35AM -0200, Rangel Reale wrote:
> I'm still having problems forking Poco and making changes in some files.
> Looks like there is some inconsistency of line endings in the repository, I
> cloned in Linux and ran a "file" command to detect line endings on source
> files, multiple files appeared as CRLF. By the .gitattributes file, all
> source files should have been converted to LF, for the current architecture.
> I'm having problems speficifally in one file on this list,
> "Data/SQLite/src/SQLiteStatementImpl.cpp". so it should be the problem.
> Is it possible to fix this in the repository?
I am new to Poco, sorry if i overlooked the obvious.

This is how other projects handle this. Quoting from the Qt docs:

Configuring Git

We are developing in a heterogeneous environment with both Unix and
Windows machines. Therefore it is imperative to have all files in the
repository in the canonical LF-only format. Therefore, Windows users
‘’‘must’‘’ run

        $ git config --global core.autocrlf true

to automatically get CRLF line endings which are suitable for the native
tools, and Unix users ‘‘should’‘ use

        $ git config --global core.autocrlf input

(this is a safety measure for the case where files with CRLF line
endings get into the file system – this can happen when archives are
unpacked, attachments saved, etc.).