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 has been updated discards c961d5fdab4585ec1bc794b71bd340364293debf (commit) via 877187bac1da8b18265d80051282fac77d4b7709 (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 (c961d5fdab4585ec1bc794b71bd340364293debf) \ N -- N -- N (877187bac1da8b18265d80051282fac77d4b7709)

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: milena/NEWS | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)

hooks/post-receive