As explained by Peter van der Does, the init command does not have the
init function, nor does it need one.

This patch tags commits on the original (release/hotfix branch) instead
of tagging the merge commit on the master branch.  This keeps the
history git-describe friendly.  (For related discussions, see #49, #85,

make the installer for msysgit search in ~/bin as well

Added 'init()' function to git-flow-{feature,release,hotfix,support}

small bug fix in gif-flow-feature

fixes pull existing feature from remote.

Fix broken link to original blog-post

Support reading the tag message from a file in release/hotfix finish

Fix init -d behaviour when master branch exists, and 1+ other branches exist, but develop does not

This option ('-f' because '-F' was already taken) maps to the 'tag -F' option, and avoids the
problem with issue #98 (https://github.com/nvie/gitflow/issues/98) on Mac

Fix init -d behaviour when master branch exists, and one or more other branch exists, but develop does not
Without this change, init picks 'master' as both the production and integration branch and fails. With it, init detects the clash and behaves the same as if only master exists, picking 'develop' as integration branch

Added 'init()' function to git-flow-{feature,release,hotfix,support}, which gets called if subargument is not help

Adding an optional (false by default) -S option to 'git flow feature finish' to allow squashing
the commit

Adding an optional (false by default) -S option to 'git flow release finish' to allow squashing
the commit

Conflicts:
	README.mdown

Signed-off-by: Vincent Driessen <vincent@3rdcloud.com>

This is done in anticipation of their discontinuing service.

Signed-off-by: Vincent Driessen <vincent@3rdcloud.com>

Adding the `eval` to force variable expansion.

Documented init -d flag and feature publish/pull

Updating the escape characters to fix + in the branch name

Since git allows for it the escape should not escape it since it then won't match the branch names correctly.