Please don't create a default README.md on git flow init

[VanNostrand]

The following two commands should create an identical result, but with git flow an unexpected side effect is created:

$ git init; git flow init -d; echo hello >> README.md | md5sum README.md
1740b74b383fed4da87331e542b7f4e8  README.md

$ git init; echo hello >> README.md | md5sum README.md
b1946ac92492d2347c6235b4d2611184  README.md

Well I guess, I am working with a very UNIX-principle biased mindset ("doing one thing and doing it well", plus "no message is good message"), so I was surprised when git flow init created a README.md in an empty working directory of a fresh git repo.
The file is also not empty, which is another side effect, but contains redundant information about something I knew when I executed got flow init.

Please don't let git flow init create any content in the working directory. If there is a use case for using templated contents that could be done with an optional command line argument.

[alexrinass]

This should, of course, not be the case. It appears to occur only when no commit exists yet—which is required to create additional branches. In such a situation, the command should return an error.

[alexrinass]

As a side note, both the original git-flow and git-flow-avh automatically initialize a Git repo and create an empty commit if no Git repo is found so I would replicate this behavior here.