You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Allen Wittenauer (JIRA)" <ji...@apache.org> on 2014/09/04 01:07:54 UTC
[jira] [Updated] (HADOOP-8911) CRLF characters in source and text
files
[ https://issues.apache.org/jira/browse/HADOOP-8911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Allen Wittenauer updated HADOOP-8911:
-------------------------------------
Fix Version/s: (was: 3.0.0)
> CRLF characters in source and text files
> ----------------------------------------
>
> Key: HADOOP-8911
> URL: https://issues.apache.org/jira/browse/HADOOP-8911
> Project: Hadoop Common
> Issue Type: Bug
> Components: build
> Affects Versions: 3.0.0, 1-win
> Reporter: Raja Aluri
> Assignee: Raja Aluri
> Fix For: 1-win, 2.0.3-alpha
>
> Attachments: HADOOP-8911.branch-1-win.patch, HADOOP-8911.branch-2.patch, HADOOP-8911.trunk.patch, HADOOP-8911.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.
> But before adding the .gitattributes file we need to normalize the existing tree, so that people when they sync after .giattributes change wont end up with a bunch of modified files in their workspace.
> 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
> I will submit a separate bug and patch for .gitattributes
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)