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 37db86920108a095aa87b2ae0be6322ee3804e49 (commit) discards 8f4ee017f9b8e2bf3541df3e464bc2d56368bf04 (commit) via 7f135958759e0b5bbbfdbedd6873ad4bda2c666a (commit) via 11434c3d5bce98164462b59d0a30c9a0219297c7 (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 (37db86920108a095aa87b2ae0be6322ee3804e49) \ N -- N -- N (7f135958759e0b5bbbfdbedd6873ad4bda2c666a) 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 ----------------------------------------------------------------- 7f13595 Add a test case to exercise the issue of Trac ticket #125. 11434c3 Improve tests on mln::border::mirror. ----------------------------------------------------------------------- Summary of changes: milena/ChangeLog | 5 +- milena/mln/border/mirror.hh | 225 +++++++++++++++++++++++-------------------- 2 files changed, 122 insertions(+), 108 deletions(-) hooks/post-receive -- Olena, a generic and efficient image processing platform