On Thu, Jul 24, 2008 at 01:39:34PM +0100, Johannes Schindelin wrote: > > Well, seems I will just continue shouting "why did you commit that > CR-ridden file?" and get shouted back with "why does this §&%&%&!° Git > tool not fix it for me automatically? Even _Subversion_ can do it." Actually, no... With Subversion, if you do not have correct auto-props then every newly added file will have incorrect end-of-lines. So, each user has to manually add all possible text extensions in the auto-props section of his/her subversion config file. In practice, it means that with SVN you have far less problems with EOLs in first few days when users just existing files, but then the problem reemerge every time when someone adds a new file... So, it is not much better... In constrast, Git provides automatic text detection and EOL conversion, but it is not enabled where it should... at least, on Windows, and for those who copies file directly from Windows through network shares or by other means. Dmitry -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
