[ https://issues.apache.org/jira/browse/SCM-885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16473597#comment-16473597 ]
Michael Osipov edited comment on SCM-885 at 5/13/18 8:34 PM: ------------------------------------------------------------- Do you think you could modify the PR to satisfiy the first three cases of [this spec|https://git-scm.com/docs/gitrevisions#_revision_range_summary]? I am reluctant to change the current, correct behavior. Git offers to many representations which cannot be covered by a generic API. was (Author: michael-o): Do you think you could modify the PR to satisfiy the first three cases of [this spec|https://git-scm.com/docs/gitrevisions#_revision_range_summary]? I am reluctant to change the current, correct behavior. Git offers to many representations which can be covered by a generic API. > 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 > Priority: Major > Fix For: waiting-for-feedback > > > 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)