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 try-next has been updated discards e70efe8043ed2830cc8df93c9dd2c18e8e440e11 (commit) discards 0dc6cfc9c85080214b1a5faa741befe50ec73b11 (commit) via 856f489ee9fbbfde026dddff7377f7a27e7c9452 (commit) via 258c4cb992df1c43678d39bd7bbe2dc4dd18f6db (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 (e70efe8043ed2830cc8df93c9dd2c18e8e440e11) \ N -- N -- N (856f489ee9fbbfde026dddff7377f7a27e7c9452) 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 ----------------------------------------------------------------- 856f489 Fix compilation in Scribo. 258c4cb Rely on Argument-Dependent Lookup (ADL) in from_to_ overloads. ----------------------------------------------------------------------- Summary of changes: milena/mln/convert/from_to.hh | 12 ++++++++---- 1 files changed, 8 insertions(+), 4 deletions(-) hooks/post-receive -- Olena, a generic and efficient image processing platform