[
https://issues.apache.org/jira/browse/SCM-885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17963535#comment-17963535
]
ASF GitHub Bot commented on SCM-885:
------------------------------------
jira-importer commented on issue #1116:
URL: https://github.com/apache/maven-scm/issues/1116#issuecomment-2964646710
**[Matthieu
Brouillard](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=mcfoggy)**
commented
there is not problem ; I fully undertsand you could have been confused. And
finally such confusion & discussions were good because in the end we will get a
better impl because using the cases described in above table we will be
backward compatible (expect for the bug fixes I will provide) and still offer
the possibility to have history fom the beginning of the repository.
I am working on the PR. As I really add more IT tests it takes more time to
me, stay tuned...
> Extend GitChangeLogCommand by using revision only
> -------------------------------------------------
>
> Key: SCM-885
> URL: https://issues.apache.org/jira/browse/SCM-885
> Project: Maven SCM (Moved to GitHub Issues)
> Issue Type: Improvement
> Components: maven-scm-provider-gitexe, maven-scm-provider-jgit
> Affects Versions: 1.9.5
> Reporter: Matthieu Brouillard
> Assignee: Michael Osipov
> Priority: Major
> Fix For: 1.10.0
>
> 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
(v8.20.10#820010)
