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 "ABE".
The branch, bernie/benchmarking has been updated discards 4060ddfc3bd29aa2b5acbcad966eb5e8a13cbe9b (commit) discards 553c3761781f5e042c8178cb81f831630369e8a1 (commit) discards edc92a6c6c90db16c5bc35cc521904335f9ae08d (commit) discards 1f29382fa4ad20a41f89220252604aaa9cea4247 (commit) discards 59a0f501c4070f2bdb9afe6c9f855cfad9b9df06 (commit) via 7779401eb9c54ca170928452892cd8424edfff6e (commit) via 675bf3f3803cbda1944e1546c5c5cf85e1200a9a (commit) via 8d30a2c508468bb534bb937bd488b18b8636d3b1 (commit) via d00fb95a1b5dbe3a84fa158df872e1d2c4c49d06 (commit) via d758ec431131655032bc7de12c0e6f266d9723c2 (commit) via a2a4b6c0560e41e2415f1f18fcae47d2d92aba19 (commit) via 84cca05ccf4aa3df6cd6773735f0914ead7b460a (commit) via b00b97f215de59b71921ab500becdfb4c44c07d0 (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 (4060ddfc3bd29aa2b5acbcad966eb5e8a13cbe9b) \ N -- N -- N (7779401eb9c54ca170928452892cd8424edfff6e)
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: config/boards/bench/arndale.json | 3 +-- config/sources.conf | 6 +++--- 2 files changed, 4 insertions(+), 5 deletions(-)
hooks/post-receive