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 branch, next has been updated discards 66bc236b2059f554c378b90d5291ca4a8aecf5b4 (commit) discards 22a659377f3b181e351428708708971c819582f7 (commit) discards 458bc7ddf290806f0a95c76da6f6d4f3c8a07737 (commit) discards 12229e66492f7947c180cf540aecd53096431bc8 (commit) discards 7378c0ddeb8c34a38d0021230a65bccfc21a6f1b (commit) via 332d48c9c25504b3cbb9451e292a98c15df17ccb (commit) via 0d3ee95d0fb3712631d81c5e6f4fb5f176617c5e (commit) via 0c3ee63ae7b133defa2e74d2573f541d68dae040 (commit) via 8f517b3a278d3742b182b67d6b50f9452dd3e519 (commit) via 2afd00967b751ef3a9fe45d2f966f35956c93520 (commit) via 969d1c74ef21b77df01b120297d4156b87183894 (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 (66bc236b2059f554c378b90d5291ca4a8aecf5b4) \ N -- N -- N (332d48c9c25504b3cbb9451e292a98c15df17ccb)
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 ----------------------------------------------------------------- -----------------------------------------------------------------------
Summary of changes: .travis.yml | 15 +++++++++++++++ 1 file changed, 15 insertions(+)
hooks/post-receive