hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Colin Patrick McCabe (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-9675) releasenotes.html always shows up as modified because of line endings issues
Date Mon, 01 Jul 2013 18:46:20 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-9675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13697058#comment-13697058

Colin Patrick McCabe commented on HADOOP-9675:

from the mailing list:

While I agree that it would be nice to fix relnotes.py, it seems to me
that setting svn:eol-style=native should fix the problem completely.
Files with this attribute set are stored internally by subversion with
all newlines as LF, and converted to CRLF as needed.  After all,
eol-style=native would not be very useful if it only applied on
checkout.  Windows users would be constantly checking in CRLF in that

I'm not an svn expert, though, and I haven't tested the above.

> 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
>            Assignee: Colin Patrick McCabe
>         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

View raw message