Jason Kankiewicz

@chhh, I had a similar problem (#355) with starting a support branch but I think it may have been caused by the specified base tag's absence in the origin repository....

@chhh, After further consideration, I think that the optional `` argument is only supposed to be a branch's name and never a tag because a hotfix branch is either supposed...

> I still think, that a hotfix/v2.x could just be created automatically and just kept there without being deleted - it would serve the role of support/v2.x branch itself. @chhh,...

> I have the same proble. I cannot create hotfix form tag and this is required for me. @joxpg, what's stopping you from first creating a support branch from that...

Isn't this functionality already provided by the `git flow release delete ` command and the shortcut `git flow delete` command (when you're already on the release branch that you wish...

> ...all the fixes should be back-merged to develop. @wilbertjoosen, You're right; a new command is needed because the `delete` command won't merge any commits that are unique to the...

What default value for the missing `` argument do you expect the command to use in its place, `master`? Being that a support branch exists for applying hotfixes to previous...

This is related to #407 in that there should be a corresponding `git flow` command for every vanilla `git` command that can potentially invalidate the "[git flow ...]" sections within...

I just ran into this same bug today. :angry:

Unfortunately, support branches are still second-class citizens because you can neither publish (#356) nor track (#368) one without resorting to bare `git` command usage. :frowning_face: