Thanks Joseph! I've added you to the AUTHORS file, too.

---

Not sure if its of interest to you, but I implemented a --defaults flag in git-flow-init so the script doesnt have to prompt for branch names.  My goal is to now make a change in my gitolite install so every new rep is initialized with the git flow model.  Resolves issue 88.

Great work on git-flow.  Im really liking it.

Joseph

Added support for using defaults without prompts when using git flow init.

In particular, this fixes the case where a dot in a version name (not
too uncommon ;)) unintentionally matches a pre-existing tag.  For
example, if these tags exist:

    1.0.1
    1.0b2

And you try to start a new release for 1.0.2, git-flow prevented it,
since the '.' matches the 'b' in 1.0b2.  This resulted in the invalid
error message:

    Tag '1.0.2' already exists. Pick another name.

Original commit message:
Allows wget to work rather than failing silently.  The actual error is
"ERROR: certificate common name `*.github.com' doesn't match requested
host name `github.com'."  Tested on Ubuntu 10.10.  Not tested on
Windows, so I haven't changed that line.
Signed-off-by: Vincent Driessen <vincent@datafox.nl>

This is the real fix for the incorrect fix that I reverted in the
previous commit.  parse_cmdline was used to DRY up the source, but this
introduced a bug because the "eval set" line changes the positional
parameters semantics, but does it in the wrong context, so the calling
function never receives the changes.

This closes at least the GitHub issues #54 and #86.

This patch was originally contributed as a workaround for the cases
where there were flags that took the first argument position.  This fix
was just plain wrong and this commit reverts it.

that should be on top.

Thanks Mark and David!

On some systems, /bin/sh is a symlink to dash. "local" here wants to
create variables for multiple words on the line. Added quotes so that
these are not treated as multiple variables.

I hope this makes it easier for people to contribute to git-flow.

By setting the environmental variable POSIXLY_CORRECT, getopt behaves
strictly POSIX-compatible.  This fixes the incorrect getopt parsing
style that breaks git-flow in several flavours of Linux.

Many thanks to Thiana for figuring this one out.

This should fix issues #28 and #29.

This fixes issue #59.

This implementation does not rely on Bash-specific functionality.

This is useful for small projects.

Simply step aside to the master branch instead.

For example, you could set the versiontag prefix to be:

    git config --global gitflow.prefix.versiontag "production/\$(date +%Y/%m/%d/)"

which would result in tag names like:

    production/2010/09/22/my-hotfix-or-feature-name

NOTE:
Although this is a useful addition in the current version of git-flow,
in a future reimplementation of it in Python, this will be replaced by
hook scripts, so be sure not to rely on this feature too much for now.