[
https://issues.apache.org/jira/browse/PROTON-618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14160355#comment-14160355
]
ASF subversion and git services commented on PROTON-618:
--------------------------------------------------------
Commit 1629675 from [~gemmellr] in branch 'proton/trunk'
[ https://svn.apache.org/r1629675 ]
PROTON-618: update line endings only, for consistency with other files
> [proton-j] some of the .java source files have crlf line endings, most dont
> ---------------------------------------------------------------------------
>
> Key: PROTON-618
> URL: https://issues.apache.org/jira/browse/PROTON-618
> Project: Qpid Proton
> Issue Type: Bug
> Affects Versions: 0.7
> Reporter: Dominic Evans
> Assignee: Robbie Gemmell
> Priority: Minor
>
> The following files are the only ones in version control (and the
> qpid-proton-0.7.tar.gz) that currently have crlf line endings:
> proton-j/src/main/java/org/apache/qpid/proton/amqp/Binary.java
> proton-j/src/main/java/org/apache/qpid/proton/amqp/Symbol.java
> proton-j/src/main/java/org/apache/qpid/proton/amqp/UnsignedByte.java
> proton-j/src/main/java/org/apache/qpid/proton/amqp/UnsignedInteger.java
> proton-j/src/main/java/org/apache/qpid/proton/amqp/UnsignedLong.java
> proton-j/src/main/java/org/apache/qpid/proton/amqp/UnsignedShort.java
> Perhaps we could modify them to match the rest of the source and be Unix LF
> only?
> It might also be worth checking in a top-level .gitattributes with '* text
> eol=lf' (assuming this also effects git-svn pushes?)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)