jira-importer commented on issue #661: URL: https://github.com/apache/maven-scm/issues/661#issuecomment-2964611904
**[Kristian Rosenvold](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=krosenvold)** commented Please note that the issue as /originally/ filed can be solved using git >= v1.6.3 using the following configuration: git config push.default current ("tracking" option may also be used to the same effect, a --global flag can also be used to make this global default) See the push.default option on the following page http://www.kernel.org/pub/software/scm/git/docs/git-config.html Git 1.6.3 was not published at the time this issue was created. As we speak I believe most platforms have >=1.6.3 in their available releases, so I am not sure this issue should be fixed for /this/ reason - although there may be other sensible use cases for this (Additionally I am also a bit sceptical at the "git fu" in use for the release plugin. I really think the "released" version shouldn't be in the history of the "master" branch, it should be a separate tag, as can be seen from the "1.2" release in the attached image (http://jira.codehaus.org/secure/attachment/47698/release_branch.jpg). The "1.2.1" as shown in the image is made with the release plugin. From the perspective of "push", I think the tag can/should be pushed, possibly even force pushed. Force could be used when re-rolling releases) -- 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: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
