current branch, if any.

This fixes #127.

Thanks for the MSysGit installer!

Installer for the Windows msysgit environment

This reverts commit fff16edd.

Set GITFLOW_DIR correctly if git-flow is a symbolic link

Thanks Kiall for the Debian package files!

Add debian/ubuntu packaging

Fixing some minor mistakes in debian/control metadata - followup to ca475abb

This allows a user to create a symbolic link to git-flow in their
personal bin directory (e.g. ~/bin) without having to add the source
tree to their $PATH or do a system install.

This fixes #53.

Signed-off-by: Stefan Naewe <stefan.naewe@googlemail.com>

- Added fetching develop branch from origin when fetch flag is on in feature finish

Fixed require_tag_absent to not break when the list of tags contains an ambiguous entry, e.g. looking for "1.0.1" in "0.1.0 0.1.1 0.1.2 1.0".

This installer:
- detects the Git installation path
- checks prereqs (git, getopt.exe)
- delete old gitflow install
- install gitflow files

"Access denied" errors are detected and the user is given advice in that case (
use full administrator rights).

Using --recursive simplifies instructions related to the submodule
initialization for shFlags.

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!