Note to self on how we created the 1.6.0/1.7.0/stable-1.6 branch in git:
sha1=f0c28b391c2ca6d8be4b7b7313042a6b3eb4dc8c git tag [-s] -m 'version 1.6.0' 1.6.0 $sha1 git tag [-s] -m 'version 1.7.0' 1.7.0 $sha1 git branch stable-1.6 $sha1 git push origin tag 1.6.0 1.7.0 stable-1.6
(Thanks Jim Meyering for working out the details)
Is that 2 tags (1.6.0 and 1.7.0) on the same sha1? what’s the reason?
Thanks for example of the ‘-m’ option, never realized it’s also here for the tag command.
That was a mistake — we moved those tags “up” each respective branch later so that the releases were correctly tagged.