Florian Klaempfl
Wed, 08 Apr 2009 06:41:47 -0700
Graeme Geldenhuys schrieb: > hehe... OK, lets try this one more time... > > On Wed, Apr 8, 2009 at 2:12 PM, Florian Klaempfl <flor...@freepascal.org> > wrote: >>> In that case, all you would need is an editor that supports Unix line >>> endings and not try and convert them to crlf as you edit the file - >> Oh, maybe at the end I should switch to linux to use git ;) ? > > Only if you want a descent OS, but I thought we were only talking > about descent editors. ;-)
As pascal shows, something proven is often better as some hype ;) > > >> Windows uses #10#13 as newline marker, period. A program which cannot >> handle this well (and svn shows that it is perfectly possible) is simply >> crap and is not suitable for windows development. > > And Linux uses #10 as newline marker, period. A program which cannot > handle this well (and git shows that it is perfectly possible) is > simply crap and is not suitable for Linux development. > > So what's you point??? Git *does* handle it correctly - it's > perfectly possible. No, if I do it wrong, nothing prevents me to do so, see below. It's the same as with merging: I didn't see any means to avoid the merging of certain changesets to a particular branch as svnmerge does. This fits exactly into my picture of git being a big design failure as a general purpose scm: besides being a posix hack (see also file names: ".gitattributes") it does not help users to avoid mistakes. I admit, as pascal programmer I like fail safe solutions, but you should too ;) >> How can I prevent that I forget this? > > By creating the .gitattributes file in the root of the project and > adding it to your project. ... and when I forget to add a file to .gitattributes, nothing helps me. Our svn server is configured to prevent adding of files without proper mime property settings. _______________________________________________ fpc-other maillist - fpc-other@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-other