jira-importer commented on issue #1116: URL: https://github.com/apache/maven-scm/issues/1116#issuecomment-2964646705
**[Matthieu Brouillard](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=mcfoggy)** commented > The usecase ..END is covered by START..END where START hast to be provided as HEAD explicitly you refused the initial PR that was assuming the same for both `..END` & `START..` because it was introducing a non compatible change. I do not understand anymore. > The last usecase for is that SCM_VERSION is END_SCM_VERSION, I'd expect users to provide HEAD to avoid ambiguity. I don't understand the sentence. Given the table above there is no ambiguity anymore because if any of the `START_SCM_VERSION` or `END_SCM_VERSION` is provided then it is the syntax `A..B` that will be used even if any of A or B is ommited (null). `git whatchanged VERSION` will only be issued when and only when both `START_SCM_VERSION` and `END_SCM_VERSION` are null I'll provide another PR that implements the table. -- 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]
