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 ffdd63fed19fc26c8807ce67a72fb42d507a9f94 (commit) discards 888cdfe7745e9f4016e0c73b64933a8162229e4a (commit) via 37db86920108a095aa87b2ae0be6322ee3804e49 (commit) via 8f4ee017f9b8e2bf3541df3e464bc2d56368bf04 (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 (ffdd63fed19fc26c8807ce67a72fb42d507a9f94) \ N -- N -- N (37db86920108a095aa87b2ae0be6322ee3804e49) 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 ----------------------------------------------------------------- 37db869 Add a test case to exercise the issue of Trac ticket #125. 8f4ee01 Various changes in mln::border::mirror. ----------------------------------------------------------------------- Summary of changes: milena/mln/border/mirror.hh | 12 +++++++++--- 1 file changed, 9 insertions(+), 3 deletions(-) hooks/post-receive -- Olena, a generic and efficient image processing platform