Peter van der Does

This is sort of implemented in my fork [git-flow AVH Edition](http://bit.ly/S2k1S2). More info about the implementation can be found at [git-flow AVH Edition Issue 43](petervanderdoes/gitflow/issues/43) ## Any updates made to...

+1 and I decided to implement this on my [fork](https://github.com/petervanderdoes), currently only in the develop branch. Also added the ability to remove the remote branch as well.

This is implemented in https://github.com/petervanderdoes/gitflow-avh It's backwards compatible with this version but adds many improvements and new features. Disclaimer: I'm the project lead for Gitflow AVH Edition

My question about this request is: how to determine on which release branch the hotfix should apply? You can't just assume the latest, well I guess you could but that...

I agree with you that I don't see the point of creating multiple release branches, but git flow release has the option to keep release branches. So it's not a...

Instead of this patch you can just set an environment variable: ``` export GIT_MERGE_AUTOEDIT=no ``` No editor will be brought up on merging.

You could add the export of the variable in git-flow and your are all set, for example after https://github.com/nvie/gitflow/blob/develop/git-flow#L41 you can add `export GIT_MERGE_AUTOEDIT=no` and it's enforced in git-flow. In...

@wnagrodzki Sourcetree has embraced the AVH Edition. It is mentioned in the acknowledgements, About -> Acknowledgements

The problem of @AD7six has been resolved in the [gitflow AVH Edition](https://github.com/petervanderdoes/gitflow) Fetching all branches from the remote before the init is a good addition and will be implemented soon...

I recommend looking at https://github.com/petervanderdoes/gitflow-avh which is able to do what you ask. Disclaimer: I'm the Project Owner of git-flow AVH Edition. gitflow-avh is integrated in many other applications and...