[
https://issues.apache.org/jira/browse/DERBY-6052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13561541#comment-13561541
]
Knut Anders Hatlen commented on DERBY-6052:
-------------------------------------------
I just ran "forrest site" three times on a Debian box. The first run took 62
seconds. The next two runs took only 26 seconds each. I don't know how to tell
whether or not it tried to fix crlf, though.
In any case, +1 to setting svn:eol-style=native on the html files under
build/site.
> Text files under build/site do not have svn:eol-style=native
> ------------------------------------------------------------
>
> Key: DERBY-6052
> URL: https://issues.apache.org/jira/browse/DERBY-6052
> Project: Derby
> Issue Type: Bug
> Components: Web Site
> Reporter: Kristian Waagan
> Assignee: Kristian Waagan
>
> Text files under build/site in the site repository, which points to [1],
> don't have the svn:eol-style=native set.
> This is a problem because:
> o it messes up your diffs on some platforms
> o building the site on some platforms ('forrest site') takes a long time (I
> observed 24 minutes on my machine)
> Regarding the second item above, 'svn st' told me there were 16121 changed
> files. I expected two files to have changed... Turns out Forrest will fix the
> line endings, and even when they are already correct all the checked in docs
> files seem to be scanned. A second run took around 5 minutes on my Windows
> machine.
> While 5 minutes is better than 24 minutes, it's still significant. I've heard
> others can build the site in 30 seconds, but I don't know if the fix crlf
> target isn't run on those platforms,or if the file system in question is a
> lot faster.
> As a reminder, people should consider downloading this file [2] to configure
> Subversion wrt EOL style.
> [1] https://svn.apache.org/repos/infra/websites/production/db/content/derby/
> [2] http://apache.org/dev/svn-eol-style.txt
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
