Actually this might be even better (no assuming a tag) # update poms $ git commit -m "[maven-release-plugin] prepare release surefire-2.12.2" $ git commit --allow-empty -m "[maven-release-plugin] copy tag for surefire-2.12.2" $ git tag surefire-2.12.2 $ git reset --hard HEAD^1 # update poms $ git commit -m "[maven-release-plugin] prepare for next development iteration"
but gitk is not showing the tag :-( perhaps you are right kristian... some dark git magic going on On 21 September 2012 13:01, Stephen Connolly < stephen.alan.conno...@gmail.com> wrote: > # update poms > $ git commit -m "[maven-release-plugin] prepare release surefire-2.12.2" > $ git checkout -b temp > $ git commit --allow-empty -m "[maven-release-plugin] copy tag for > surefire-2.12.2" > $ git tag surefire-2.12.2 > $ git checkout master > # update poms > $ git commit -m "[maven-release-plugin] prepare for next development > iteration" >
