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 920ad47be19867ad5567a89f5cb1891a077e7b39 (commit) via 4733be7a8971b37d3bd71089646a14afff5548b3 (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 (920ad47be19867ad5567a89f5cb1891a077e7b39) \ N -- N -- N (4733be7a8971b37d3bd71089646a14afff5548b3) 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 ----------------------------------------------------------------- 4733be7 Milena: New test exercising fun_image with RGB component functions. ----------------------------------------------------------------------- Summary of changes: milena/ChangeLog | 8 ++++++++ 1 file changed, 8 insertions(+) hooks/post-receive -- Olena, a generic and efficient image processing platform