[
https://issues.apache.org/jira/browse/PLUTO-456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12554931
]
Elliot Metsger commented on PLUTO-456:
--------------------------------------
Used this script, first using file to make sure the extensions weren't lying.
for ext in apt css dtd fml html inc js jsp properties tld txt xml xsd java ;
do
for f in `find . -name "*.$ext"` ; do
cp $f foo ; perl -np -e "s:\r\n:\n:g" < foo > $f ;
svn ps svn:eol-style native $f
done
done
> fix line endings on files.
> --------------------------
>
> Key: PLUTO-456
> URL: https://issues.apache.org/jira/browse/PLUTO-456
> Project: Pluto
> Issue Type: Improvement
> Components: general
> Affects Versions: 1.1.4
> Reporter: Elliot Metsger
> Assignee: Elliot Metsger
> Priority: Minor
> Fix For: 1.2.0, 1.1.5, 1.1-286-trunk-merge
>
>
> Line endings are inconsistent on the java source files, and I suspect there
> are inconsistent line endings on other files as well in the pluto project.
> It's annoying, and also impedes patch application.
> I plan to update the line endings on text files ending with the following
> extensions, and then setting the svn property 'svn:eol-style' to "native" for
> those files.
> apt
> css
> dtd
> fml
> html
> inc
> js
> jsp
> properties
> tld
> txt
> xml
> xsd
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
