- The `git config` method did not respect branch.autosetuprebase
  - The --set-upstream option was introduced in git 1.7.0

  - must #dup frozen strings for use in Gem::Specification
  - use absolute paths with require since $LOAD_PATH no longer contains '.'

… version of RubyGems

* Florent2/patch-1:
  --include-dependencies is now default and will be removed in a future version of RubyGems

Use `git branch --set-upstream` instead of `git config`

… repo)

Imagine a typical use case for grb:

* User moves to a project dir (~/myproj)
* User uses grb (grb create funtimes)
* grb executes Bundler.setup, which munges Ruby's load path to match myproj's Gemfile.lock
* grb tries to require "rainbow," which isn't in myproj's Gemfile.lock
* grb dies

Gem dependencies are better handled by Rubygems during install, and later by Bundler when running against an
actual app's Gemfile.

Per Yehuda: http://yehudakatz.com/2010/12/16/clarifying-the-roles-of-the-gemspec-and-gemfile/

Per Yehuda: http://yehudakatz.com/2010/12/16/clarifying-the-roles-of-the-gemspec-and-gemfile/

Fix dependency management

Requiring rubygems in lib/ is bad, hmmkay?