[Lazarus] EOL character used in .lfm files keep changing

[Joost van der Sluis]

Op donderdag 11-06-2009 om 13:20 uur [tijdzone +0200], schreef Graeme
Geldenhuys:
> 
> 
> Fixed. Git is more that just a source code repository (ala
> SubVersion),
> it is more like a file system with integrity checking all built in.
> What
> you put in, is exactly (guaranteed by SHA1 checks) what you will get
> out. No silent modifications of files. In todays software world, all
> text programs (editors etc..) should be able to handle any text files
> with whatever EOL characters. If not, that text editor isn't worth
> using.

Maybe in your -unix-centric- world. But not in the real
-windows-centric- world. And we are aiming to build some tools which are
really cross-platform. And not with all kind of tricks.

And we want to do this right. This implies conversion from line-endings
between platforms. Subversion can do this (because it's build with the
same mindset: cross-platform) Git can't, because it's hacked together
for one platform. Maybe some people added windows-support later on, but
it's not designed to do so, like gcc programs using mingw/(that other
framework).

I don't know how others are thinging about this, but I think it would be
better when you stop cluttering this mailinglists with all your
git-problems and git-promo-talk.

As you said, we aggree to disaggree. You want to use your own tools,
then don't bother us with your tool's problems.

Joost.