[ 
https://issues.apache.org/jira/browse/GROOVY-6327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15090818#comment-15090818
 ] 

ASF GitHub Bot commented on GROOVY-6327:
----------------------------------------

GitHub user jwagenleitner opened a pull request:

    https://github.com/apache/groovy/pull/236

    GROOVY-6327 - normalize line endings

    Use `.gitattributes` to normalize line endings 
(http://git-scm.com/docs/gitattributes).  Besides adding the `.gitattributes` 
file also had it identify existing files with `CRLF` and converted them to `LF`.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/jwagenleitner/groovy GROOVY-6327

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/groovy/pull/236.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #236
    
----
commit 08ce3b3f95f5a7ee5dba6d3bcecf9ab429b121db
Author: John Wagenleitner <jwagenleit...@apache.org>
Date:   2016-01-09T21:54:39Z

    GROOVY-6327 - use .gitattributes to enforce line endings

commit db9440baa49713bcefd9f8de3098f68d0902a4d4
Author: John Wagenleitner <jwagenleit...@apache.org>
Date:   2016-01-09T22:43:47Z

    GROOVY-6327 - EOL conversion using .gitattributes

----


> Some source files still have \r\n line endings
> ----------------------------------------------
>
>                 Key: GROOVY-6327
>                 URL: https://issues.apache.org/jira/browse/GROOVY-6327
>             Project: Groovy
>          Issue Type: Bug
>            Reporter: Russel Winder
>
> Git policy is that all files should only use \n line endings (UNIX standard) 
> and that Windows users will have local transformation to \r\n on checkout of 
> a working tree, and \r\n conversion to \n on commit.
> Many of the Groovy codebase files have \n line endings, but a large number 
> have \r\n and this is problematic.
> Making the change needs to be done by someone with permissions as an atomic 
> action on mainline head.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to