From: "Jim Fulton" <[EMAIL PROTECTED]> > I found this to be so unbelievable, that I had to resoearch it myself. [...] > unbelievable, I couldn't help it.
> > I think we'll have to develop a standard set of config file settings like > > that for committers to add to their personal svn configs -- Eh. WHAT!?! OK, that there are settings like these, but aren't they configured on the server? They are CLIENT side? That is very weird. > I think the "real" answer, the answer that the svn (and arch) developers believe > in the heart of hearts is that windows users should be using tools that understand, > well, understand and always produce Unix line endings. Well, but that is also a setting that needs to be handled. I use TextPad which conserves line endings. But when I create a new file, it would typically save it with windows endings, unless I say so.. > Is it practical to require windows users to use tools that understand and produce > Unix line endings? Maybe more practical than forcing them to have specific SVN settings, but only slightly so... > I suppose it could. I think that a post-commit script could inspect new files and, > for any new file that has no mine-type property, or has one with a text type, > set the svn:eol-style proprty to native. It would have to do this in a separate > transaction. I think this is the only possible solution... _______________________________________________ Zope-Dev maillist - [EMAIL PROTECTED] http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )