This fixes issue #59.
…ject. See the README file for instructions on how to use it.
…nixy ``prefix''. There is no need to install git-flow inside git's libexec dir by default. It just needs to be *somewhere* on the PATH.
The only exception to the rule is git-flow-support, which has an explicitly required <base> argument (since we cannot deduce a sane default name for base). Furthermore, these <base> arguments are checked to refer to commits on: - develop (for feature, release) - master (for hotfix, support) Removed any occurrences of optional <base> arguments in finish subactions. The finishing target branches are clearly defined by the model. The <base> argument will probably confuse users. If they want the power to merge those feature branches into *other* branches then develop, for example, they can still use the magical power of Git itself for that. Gitflow should not provide such support.
…e found, use the default. Variable GIT_EXEC_PATH remains overwritable explicitly when given as a command to 'make'.