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 "Olena, a generic and efficient image processing platform".

The branch next-next has been updated discards 23f310d3c2e77582df2964eed642e30f77623e13 (commit) discards 99dae6cbdd98a1af94fe3e229d4200af0e605e9d (commit) via 7c25953a8c1e0d82f2c31696ae94c1bc616281e1 (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 (23f310d3c2e77582df2964eed642e30f77623e13) \ N -- N -- N (7c25953a8c1e0d82f2c31696ae94c1bc616281e1)

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 ----------------------------------------------------------------- No new revisions were added by this update. -----------------------------------------------------------------------

Summary of changes:

hooks/post-receive