[
https://issues.apache.org/jira/browse/PIVOT-263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12751007#action_12751007
]
Todd Volkert commented on PIVOT-263:
------------------------------------
I just executed the following commands on the v1.3-rc2 tag. I'll now update
the trunk.
find . -name \*.json -exec svn ps svn:eol-style native {} \;
find . -name \*.wtkx -exec svn ps svn:eol-style native {} \;
find . -name \*.html -exec svn ps svn:eol-style native {} \;
find . -name \*.properties -exec svn ps svn:eol-style native {} \;
find . -name \*.xml -exec svn ps svn:eol-style native {} \;
find . -name \*.java -exec svn ps svn:eol-style native {} \;
find . -name \*.csv -exec svn ps svn:eol-style native {} \;
find . -name \*.css -exec svn ps svn:eol-style native {} \;
find . -name \*.wtkd -exec svn ps svn:eol-style native {} \;
find . -name \*.wtkx -exec svn ps svn:mime-type text/xml {} \;
find . -name \*.xml -exec svn ps svn:mime-type text/xml {} \;
find . -name \*.wtkd -exec svn ps svn:mime-type text/xml {} \;
find . -name \*.png -exec svn ps svn:mime-type image/png {} \;
find . -name \*.jpg -exec svn ps svn:mime-type image/jpeg {} \;
find . -name \*.json -exec svn ps svn:mime-type application/json {} \;
find . -name \*.css -exec svn ps svn:mime-type text/css {} \;
find . -name \*.jar -exec svn ps svn:mime-type application/java-archive {} \;
> SVN properties missing for lots of files
> ----------------------------------------
>
> Key: PIVOT-263
> URL: https://issues.apache.org/jira/browse/PIVOT-263
> Project: Pivot
> Issue Type: Bug
> Components: project
> Reporter: Sebb
> Assignee: Todd Volkert
> Fix For: 1.3.1
>
> Attachments: v1.3-rc2.sh
>
>
> Lots of SVN EOL properties are missing.
> See:
> http://www.apache.org/dev/version-control.html#https-svn-config
> If you don't set the eol-style native where appropriate, and SVN checkin is
> performed from OSes with differing EOL defaults, then SVN is likely to show
> spurious differences. A one-line change can show up as changes to every
> single line, which makes following SVN history very difficult. Since one
> cannot limit SVN checkins to a single OS EOL-type, the SVN property is needed.
> Attached file (to follow) was generated from the v1.3-rc2 tag, but presumably
> also applies to trunk, which is where the changes should be applied.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
