[arch-projects] [devtools] [GIT] The official devtools repository branch master updated. 20180531-7-g65b50da

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "The official devtools repository". The branch, master has been updated discards 450e6af53b9e429b894a4b04b03d45ddae1a9786 (commit) via 65b50dac40fff6032e8e6a28a2b7bf0a6482bf2e (commit) via 799376904de77c2fb862fc559c60489b37e72232 (commit) This update added new revisions after undoing existing revisions. That is to say, the old revision is not a strict subset of the new revision. This situation occurs when you --force push a change and generate a repository containing something like this: * -- * -- B -- O -- O -- O (450e6af53b9e429b894a4b04b03d45ddae1a9786) \ N -- N -- N (65b50dac40fff6032e8e6a28a2b7bf0a6482bf2e) When this happens we assume that you've already had alert emails for all of the O revisions, and so we here report only the revisions in the N branch from the common base, B. Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log ----------------------------------------------------------------- commit 65b50dac40fff6032e8e6a28a2b7bf0a6482bf2e Author: Levente Polyak Date: Tue Jan 22 02:17:56 2019 +0100 ci: adding travis support for basic check commit 799376904de77c2fb862fc559c60489b37e72232 Author: Levente Polyak Date: Tue Jan 22 03:10:08 2019 +0100 find-libdeps: in functions use return instead of continue to abort Even if continue would work, it does exactly the same as a return in the way this function is being used. ----------------------------------------------------------------------- Summary of changes: .travis.yml | 6 ++++-- find-libdeps.in | 2 +- 2 files changed, 5 insertions(+), 3 deletions(-) hooks/post-receive -- The official devtools repository