Add rbx-2.2.9, 2.2.8 was skipped due to broken wrappers.

Fix `fetch_git` with `--keep`

Update existing git repo if exists, or clone if not exists.
The destination repo might exist if the `--keep` was supplied for `ruby-build`.

OpenSSL library updated to 1.0.1h

Previous versions of the library contain a vulnerability CVE-2014-0224.

The script handles bumping up the version number, committing, tagging
and updating the Homebrew formula. The last step requires `hub` to be
installed in order to submit a pull request to Homebrew.

/cc @sferik @hsbt

[ci skip]

Fixes #548, closes #551

This is so any 3rd-party definitions continue to work even if they have
MD5 checksums embedded.

A more secure hashing algorithm makes it less feasible to serve up a
modified tarball that matches the same checksum.

See the discussion in #548

add rbx-2.2.7

added definition of 1.9.3-p547

This reverts commit d45f1451, reversing
changes made to 13de5110.

Added definition of 2.0.0-p481

Ruby 2.1.2 is released!

link the latest log to /tmp/ruby-build.latest.log

Make the downloading message print the actual file name, not just the package name plus .tar.gz.

Correct the JRuby 9000 snapshot directory name.

`mktemp -t ruby-patch`, although working on OS X, fails on Travis CI
with the message "too few X's in template".

https://travis-ci.org/sstephenson/ruby-build/builds/23436088

[picture of I Have No Idea What I'm Doing dog]

https://travis-ci.org/sstephenson/ruby-build/builds/23435342

Filenames in git diff patches are prefixed by default by "a/" (source)
and "b/" destination. Such patches don't work with ruby-builds `--patch`
option since it internally uses `patch -p0`.

Prior workarounds were to use either an intermediate step:

    filterdiff --strip=1

or to generate the patch without the prefix in the first place:

    git diff --no-prefix ...

Now, git diff patches are detected by searching for this pattern:

    diff --git a/...

And `patch -p1` is used by default in such cases to strip the 1st
component of filename paths.

Fixes #521, closes #484

From patch(1):

    -f  or  --force
       Assume that the user knows exactly what he or she is doing, and do  not
       ask any questions.  Skip patches whose headers do not say which file is
       to be patched; patch files even though they have the wrong version  for
       the Prereq: line in the patch; and assume that patches are not reversed
       even if they look like they are.  This option does not suppress commen-
       tary; use -s for that.

Fixes #555

Prefer ggrep for grep invocations that use GNU extensions.

Fixes ruby-build on Solaris 11.1