Jason Karns d5de31f490 TRAVIS_COMMIT_RANGE is correct now ... According to https://github.com/travis-ci/travis-ci/issues/1719 (closed by https://github.com/travis-ci/travis-core/pull/383), the behavior of $TRAVIS_COMMIT_RANGE should be correct now. We should be able to use it directly.		2015-11-04 11:05:41 -05:00
..
brew-publish	Update brew-publish to be sha256-aware	2015-05-19 21:33:47 +02:00
mirror	Improve script/mirror argument handling	2014-09-08 09:15:52 -07:00
release	Add release script	2014-05-26 23:34:26 +07:00
s3-put	Keep mirror up-to-date using Travis CI	2013-10-24 17:44:41 +02:00
test	TRAVIS_COMMIT_RANGE is correct now	2015-11-04 11:05:41 -05:00