if you look at committer environment [1], you'll see that there is a subversion configuration with precisely svn-eol-style.txt That's the default properties developer's svn client sets on files: here is the way properties are defined when adding a file to svn, even if SCM API doesn't tell anything about it.
And when svn:eol-style=native, svn doesn't like if the file contains non-native EOLs. Then I'm sure now that the normalizeNewline method should use native EOL: svn will do the conversion if the committer added the file from Windows. The checkout by svnpubsub being done by a Unix box, Unix EOLs will appear on the site Regards, Hervé Le jeudi 1 mars 2012 13:46:55 Chris Graham a écrit : > I'm confused. > > HTML is a text file, so what does it's EOL style matter? > > But you address your other question, the only way that I know is to do a > propset of svn:eol-style. > > And I am not aware that the SCM API has the facility to do this. > > I'm pretty sure (as that's where I've been poking around lately) that not > even the svn provider touches properties, but there are a few TODO comments > in there that indicate that it could be done. > > -Chris > > On Thu, Mar 1, 2012 at 12:18 PM, Benson Margulies <[email protected]>wrote: > > On the subject of newlines: personally, I think that Windows newlines > > in HTML files are evil. However, if that is an exotic belief on my > > part, I don't mind changing the code to normalize to native. It would > > be good to know what the svn eol-style is, but I don't see how do do > > that through scm. > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
