[Olena-patches] olena: branch exp/stretch_inplace updated: olena-2.0-555-g141d002

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 exp/stretch_inplace has been updated discards 357bde878da59be0f237a61b541b55baab3dae79 (commit) discards c54e470a637308911754f01dff20139f9d51ceb8 (commit) discards 6dbc5e12a4e8532e5432f4e7697cdd7476d92baa (commit) discards 9a6e78a307966abfeac00367a2dec9d5dd06c2d8 (commit) discards 1a03222386ba66855e27dcf3dd6c8e3cf2c9aae7 (commit) via 141d002bbb7d036ad72b651ff32973cbe5bc399d (commit) via 0918485a18185e62abbeaba40f9d140d1f4499e1 (commit) via e279a62f19ac337151146779edd91834ef59bd44 (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 (357bde878da59be0f237a61b541b55baab3dae79) \ N -- N -- N (141d002bbb7d036ad72b651ff32973cbe5bc399d) 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 ----------------------------------------------------------------- 141d002 Regen generated files in Milena. 0918485 NEWS: Add notification for data::stretch_inplace. e279a62 Add data::stretch_inplace. ----------------------------------------------------------------------- Summary of changes: milena/ChangeLog | 6 ++---- milena/headers.mk | 4 ---- milena/tests/unit_test/unit-tests.mk | 4 ---- 3 files changed, 2 insertions(+), 12 deletions(-) hooks/post-receive -- Olena, a generic and efficient image processing platform