[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)
[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 ] Suresh Srinivas updated HADOOP-8911: Hadoop Flags: Reviewed > 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: 3.0.0, 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 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
[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 ] Suresh Srinivas updated HADOOP-8911: Resolution: Fixed Fix Version/s: 2.0.3-alpha 1-win 3.0.0 Status: Resolved (was: Patch Available) I committed the patch to trunk, branch-2 and 1-win. Thank you Raja for the patch. > 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: 3.0.0, 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 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
[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 ] Suresh Srinivas updated HADOOP-8911: Attachment: HADOOP-8911.trunk.patch attaching the patch again to see if jenkins picks up the correct patch. > 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 > 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 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
[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 ] Suresh Srinivas updated HADOOP-8911: Affects Version/s: 3.0.0 Fix Version/s: (was: 1-win) > 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 > Attachments: HADOOP-8911.branch-1-win.patch, > HADOOP-8911.branch-2.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 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
[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 ] Raja Aluri updated HADOOP-8911: --- Attachment: (was: HADOOP-8911.patch) > 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 > > Attachments: HADOOP-8911.branch-1-win.patch, > HADOOP-8911.branch-2.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 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
[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 ] Raja Aluri updated HADOOP-8911: --- Attachment: HADOOP-8911.trunk.patch HADOOP-8911.branch-2.patch HADOOP-8911.branch-1-win.patch > 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 > > Attachments: HADOOP-8911.branch-1-win.patch, > HADOOP-8911.branch-2.patch, HADOOP-8911.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 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
[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 ] Raja Aluri updated HADOOP-8911: --- Target Version/s: 1-win Status: Patch Available (was: Open) Please take a look. > 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 > > Attachments: HADOOP-8911.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 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
[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 ] Raja Aluri updated HADOOP-8911: --- Attachment: HADOOP-8911.patch > 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 > > Attachments: HADOOP-8911.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 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
