[ https://issues.apache.org/jira/browse/SCM-885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16486818#comment-16486818 ]
Matthieu Brouillard commented on SCM-885: ----------------------------------------- Hi Mickael, * regarding the `.gitattributes`, if I defined both the binary and EOL for the repositories I added it is because: ** it happened that some files were recognized as text instead of binary ** some text files, extracted with CR+LF on my windows machine, were causing troubles and lead to unrecognized git repo. Forcing LF resolved the pb. * looks like the hooks were not that important ;) Go ahead otherwise. > GitChangeLogCommand is wrong when only endVersion is set > -------------------------------------------------------- > > Key: SCM-885 > URL: https://issues.apache.org/jira/browse/SCM-885 > Project: Maven SCM > Issue Type: Bug > Components: maven-scm-provider-gitexe > Affects Versions: 1.9.5 > Reporter: Matthieu Brouillard > Assignee: Michael Osipov > Priority: Major > Fix For: 1.9.6 > > Attachments: scm-885-different-behavior-exe-jgit-patch.diff > > > Invoking execution of a GitChangeLogCommand where only the end revision has > been set produces a wrong out. > +Actual result:+ > {{git whatchanged --date=iso ..END_REVISION_SHA1 -- PROJECT_PATH}} > +Expected result:+ only the end revison SHA1 is used without the two dots > {{git whatchanged --date=iso END_REVISION_SHA1 -- PROJECT_PATH}} -- This message was sent by Atlassian JIRA (v7.6.3#76005)