print results from each suite
Expand path when setting local override
CONTRIBUTE.md -> CONTRIBUTING.md to take advantage of github feature

Github allows you to have a link displayed when a contributor creates an
issue or pull request. Described on Github blog:
https://github.com/blog/1184-contributing-guidelines
allow PATH through sudo on rails travis workers
reword readme

  - remove upgrading from 0.8 and 0.9
  - reword intro paragraph
  - move build badge to the right of the title
Merge pull request #2207 from rohit/rename_contribute_contributing

CONTRIBUTE.md -> CONTRIBUTING.md to take advantage of github feature

[ci skip]
cut out the bit.ly middleman [ci skip]
Merge pull request #2205 from gkop/expand-local-override-paths

Expand path when setting local override
Merge pull request #2202 from rohit/warn_on_no_gem_folder

Warn if path to gem no longer exists
Merge pull request #2201 from banyan/consistent-naming

Consistent naming
specs in doc format by default
use rubygems integration
Compensate for Rubygems' usage of .gemrc sources
whitespace
remove
update changelog
explain that removing broken gems can fix things
restore CONTRIBUTE, but create new CONTRIBUTING

Since CONTRIBUTING is linked from the new issue page on github,
I've changed it to point to ISSUES, CONTRIBUTE, and the IRC channel
and mailing list. Most helpful thing I can think of for now.
Process gemspecs for gems cached from Git

This commit loads gemspecs for gems cached from Git repositories after
checkout, and replaces their contents with the results of calling
#to_ruby on the resulting Gem::Specification. This lets us remove the
(potentially huge) '.git' directories from the cache and avoid errors
for gems whose gemspecs shell out to Git.
only delete cached .gits once instead of once per spec