jira-importer commented on issue #1116: URL: https://github.com/apache/maven-scm/issues/1116#issuecomment-2964646671
**[Matthieu Brouillard](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=mcfoggy)** commented With the patch it is clear that calling GitChangeLogCommand#createCommandLine() with a null startVersion will not result anymore in issuing the git log command `..EndVersion` and thus will not result anymore in being interpreted by `HEAD..EndVersion`. But still, the ones who will want to retrieve the log between HEAD and EndVersion will be able to do so by explicitly use "HEAD" as the start version. Additionaly the ones, like me, expecting to be able to query the log between the initial commit (unknown/null startVersion) of a repository and a given commit (even HEAD) can do it. Instead of changing the interpretation like the patch does perhaps that you prefer a new API to allow to query from the origin(first commit). This way the enhancement will be backward compatible (even if non intuitive IMHO). The use case for me is that we have a maven-plugin (that delegates to maven-scm API) to compute between two calls what has changed in term of commits on a project. But the first time we query the log we have no initial commit (thus starVersion null) and we want the log between the inital commit and HEAD. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
