[
https://issues.apache.org/jira/browse/SCM-610?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17962205#comment-17962205
]
ASF GitHub Bot commented on SCM-610:
------------------------------------
jira-importer commented on issue #813:
URL: https://github.com/apache/maven-scm/issues/813#issuecomment-2964625479
**[Ringo De
Smet](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=ringods)**
commented
I started working on this one. Progress can be monitored here:
https://github.com/ringods/maven-scm/tree/SCM-610
> Use 'hg log --date' for changelog generation on a date range
> ------------------------------------------------------------
>
> Key: SCM-610
> URL: https://issues.apache.org/jira/browse/SCM-610
> Project: Maven SCM (Moved to GitHub Issues)
> Issue Type: Improvement
> Components: maven-scm-provider-mercurial (hg)
> Affects Versions: 1.4
> Reporter: Ringo De Smet
> Priority: Major
>
> The current implementation of the ChangeLogCommand for hg repositories first
> gets the commit info for the complete repository, only filtering on the dates
> afterwards in the Java level. The 'hg' binary has the option --date since
> version 0.9.2, which is the version listed as the minimum version this
> provider is compatible with.
> Running "hg help dates" gives you an overview of the options one has to
> specify a date range on the command line. The provider should be updated to
> use the 'hg' feature instead of filtering itself.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
