Mailing-List: contact common-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-dev@hadoop.apache.org
Date: Wed, 10 Oct 2012 18:07:03 +0000 (UTC)
From: "Raja Aluri (JIRA)" <jira@apache.org>
To: common-dev@hadoop.apache.org
Message-ID: <2114268307.21165.1349892423668.JavaMail.jiratomcat@arcas>
Subject: [jira] [Created] (HADOOP-8911) CRLF characters in source and text
 files
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Raja Aluri created HADOOP-8911:
----------------------------------

             Summary: 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: 1-win
            Reporter: Raja Aluri
             Fix For: 1-win


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