[
https://issues.apache.org/jira/browse/HADOOP-8912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13474653#comment-13474653
]
Aaron T. Myers commented on HADOOP-8912:
----------------------------------------
Ah, got it. Thanks for the explanation. It will help for those developers who
clone the git repo and `git add ...' their files before generating a patch. In
that case, it will help somewhat to commit this, but it won't solve the problem
100% of the time.
Raja, do you happen to know if there's a semantically equivalent thing we could
do for svn, to ensure that committers don't check in bad line endings?
> adding .gitattributes file to prevent CRLF and LF mismatches for source and
> text files
> --------------------------------------------------------------------------------------
>
> Key: HADOOP-8912
> URL: https://issues.apache.org/jira/browse/HADOOP-8912
> Project: Hadoop Common
> Issue Type: Bug
> Components: build
> Affects Versions: 2.0.0-alpha, 1-win
> Reporter: Raja Aluri
> Assignee: Raja Aluri
> Attachments: HADOOP-8912.branch-1-win.patch,
> HADOOP-8912.branch-2.patch, HADOOP-8912.trunk.patch
>
>
> Source code in hadoop-common repo has a bunch of files that have CRLF endings.
> With more development happening on windows there is a higher chance of more
> CRLF files getting into the source tree.
> I would like to avoid that by creating .gitattributes file which prevents
> sources from having CRLF entries in text files.
> I am adding a couple of links here to give more primer on what exactly is the
> issue and how we are trying to fix it.
> # http://git-scm.com/docs/gitattributes#_checking_out_and_checking_in
> #
> http://stackoverflow.com/questions/170961/whats-the-best-crlf-handling-strategy-with-git
>
> This issue for adding .gitattributes file to the tree.
--
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
