[jira] [Updated] (HADOOP-9675) releasenotes.html always shows up as modified because of line endings issues

["Colin Patrick McCabe (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/HADOOP-9675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Colin Patrick McCabe updated HADOOP-9675:
-----------------------------------------

    Attachment: HADOOP-9675.001.patch

This patch runs {{dos2unix}} on {{releasenotes.html}} and then sets {{svn:eol-style}} to {{native}} on it and other HTML files.

>From the subversion manual, here is a description of eol-style native:

bq. This causes the file to contain the EOL markers that are native to the operating system on which Subversion was run. In other words, if a user on a Windows machine checks out a working copy that contains a file with an svn:eol-style property set to native, that file will contain CRLF EOL markers. A Unix user checking out a working copy that contains the same file will see LF EOL markers in his copy of the file.
                
> releasenotes.html always shows up as modified because of line endings issues
> ----------------------------------------------------------------------------
>
>                 Key: HADOOP-9675
>                 URL: https://issues.apache.org/jira/browse/HADOOP-9675
>             Project: Hadoop Common
>          Issue Type: Improvement
>    Affects Versions: 2.1.0-beta
>            Reporter: Sandy Ryza
>         Attachments: HADOOP-9675.001.patch
>
>
> hadoop-common-project/hadoop-common/src/main/docs/releasenotes.html
> shows up as modified even though I haven't touched it, and I can't check it out or reset to a previous version to make that go away.  The only thing I can do to neutralize it is to put it in a dummy commit, but I have to do this every time I switch branches or rebase.
> This appears to have began after the release notes commit  (8c5676830bb176157b2dc28c48cd3dd0a9712741), and must be due to a line endings change.

--
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