[
https://issues.apache.org/jira/browse/SCM-454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17961609#comment-17961609
]
ASF GitHub Bot commented on SCM-454:
------------------------------------
jira-importer opened a new issue, #670:
URL: https://github.com/apache/maven-scm/issues/670
**[Mark
Struberg](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=struberg)**
opened
**[SCM-454](https://issues.apache.org/jira/browse/SCM-454?redirect=false)** and
commented
The current GitChangeLogCommand always uses --since and --until parameters
for start and end version.
Since those parameters may only be used for date ranges, we have to use the
[start]..[end]
syntax.
---
**Affects:** 1.2
**Attachments:**
-
[SCM-454.patch](https://issues.apache.org/jira/secure/attachment/12718749/SCM-454.patch)
(_9.15 kB_)
> GitChangelogCommand doesn't support tag ranges yet
> --------------------------------------------------
>
> Key: SCM-454
> URL: https://issues.apache.org/jira/browse/SCM-454
> Project: Maven SCM (Moved to GitHub Issues)
> Issue Type: Bug
> Components: maven-scm-provider-gitexe
> Affects Versions: 1.2
> Reporter: Mark Struberg
> Assignee: Olivier Lamy
> Priority: Major
> Fix For: 1.3
>
> Attachments: SCM-454.patch
>
>
> The current GitChangeLogCommand always uses --since and --until parameters
> for start and end version.
> Since those parameters may only be used for date ranges, we have to use the
> [start]..[end]
> syntax.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
