Since Travis runs as a batch job and logs are typically looked at
after-the-fact (if at all), there's not any point to seeing progress
when cloning git repos.

Signed-off-by: Philip Prindeville <philipp@redfish-solutions.com>

restarting a build doesn't update .travis.yml but does update .travis_do.sh ...

Signed-off-by: Etienne Champetier <champetier.etienne@gmail.com>

if the merge-base is not in the initial clone,
git diff / git rev-list will return funky results

Signed-off-by: Etienne Champetier <champetier.etienne@gmail.com>

Signed-off-by: Etienne Champetier <champetier.etienne@gmail.com>

It's just a minor optimization of the build.
No need to clone up to 50 revisions back (travis default)

Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>

Travis will run the following steps for every new or modified package:

- mkdir tempdir
- unpack SDK
- make download
- make check

make download will download the source code.
make check will do certain checks. Atm only checking the validity of
PKG_HASH.

Signed-off-by: Alexander Couzens <lynxis@fe80.eu>