Revisiones git-flow con versiones semánticas

Siguiendo el tutorial de Jeff en http://jeffkreeftmeijer.com/2010/why-arent-you-using-git-flow/ , inicié git flow con la configuration estándar:

[~/tmp/test] $ git init Initialized empty Git repository in /Users/nrm/tmp/test/.git/ [~/tmp/test (master)] $ git flow init No branches exist yet. Base branches must be created now. Branch name for production releases: [master] Branch name for "next release" development: [develop] How to name your supporting branch prefixes? Feature branches? [feature/] Release branches? [release/] Hotfix branches? [hotfix/] Support branches? [support/] Version tag prefix? [] [~/tmp/test (develop)] $ 

Sigo el tutorial hasta la sección "Código de producción de Hotfixing". Allí la twig de la revisión se llama "activos":

 $ git flow hotfix start assets Switched to a new branch 'hotfix/assets' Summary of actions: - A new branch 'hotfix/assets' was created, based on 'master' - You are now on branch 'hotfix/assets' Follow-up actions: - Bump the version number now! - Start committing your hot fixes - When done, run: git flow hotfix finish 'assets' 

PERO, cuando se cierra la twig de la revisión, el tutorial indica que The hotfix was tagged '0.1.1' . ¿Cómo? Estoy usando git-flow: stable 0.4.1 .

Cuando cierro el hotfix por git flow hotfix finish 'assets' , entonces la label es igual al nombre de la twig de la revisión:

 $ git flow hotfix finish assets ^^^^^^ Switched to branch 'master' Merge made by the 'recursive' strategy. assets.txt | 1 + 1 file changed, 1 insertion(+) create mode 100644 assets.txt Switched to branch 'develop' Merge made by the 'recursive' strategy. assets.txt | 1 + 1 file changed, 1 insertion(+) create mode 100644 assets.txt Deleted branch hotfix/assets (was 08edb94). Summary of actions: - Latest objects have been fetched from 'origin' - Hotfix branch has been merged into 'master' - The hotfix was tagged 'assets' ^^^^^^^^^^^^^^^ - Hotfix branch has been back-merged into 'develop' - Hotfix branch 'hotfix/assets' has been deleted 

En realidad, quiero tener ambos. Denomine una twig de revisión con alguna cadena (como "assets" en el ejemplo) independientemente del nombre de la label. Algo como

 $ git flow hotfix finish assets --with-tag 1.0.1 

Resultando en

 $ git flow hotfix finish assets --with-tag 1.0.1 Switched to branch 'master' Merge made by the 'recursive' strategy. assets.txt | 1 + 1 file changed, 1 insertion(+) create mode 100644 assets.txt Switched to branch 'develop' Merge made by the 'recursive' strategy. assets.txt | 1 + 1 file changed, 1 insertion(+) create mode 100644 assets.txt Deleted branch hotfix/assets (was 08edb94). ^^^^^^^^^^^^^ Summary of actions: - Latest objects have been fetched from 'origin' - Hotfix branch has been merged into 'master' - The hotfix was tagged '1.0.1' ^^^^^ - Hotfix branch has been back-merged into 'develop' - Hotfix branch 'hotfix/assets' has been deleted ^^^^^^^^^^^^^ 

¿Alguna sugerencia?