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 974162bb578fd0e49dadd6be3007a0f81b0231d2 (commit) discards f5f0cfb89d8d6e4c4c4dba01333d548ddda44675 (commit) via 5ec622732f36db381fd3cead7f88c448e0119359 (commit) via 84106cfffb04189d1e3bbdd527c06e93b6c24d14 (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 (974162bb578fd0e49dadd6be3007a0f81b0231d2) \ N -- N -- N (5ec622732f36db381fd3cead7f88c448e0119359) 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 ----------------------------------------------------------------- 5ec6227 Make dynamic-use-of-static-c++ more compatible with BSD Make. 84106cf Make Swilena more compatible with BSD Make. ----------------------------------------------------------------------- Summary of changes: swilena/python/Makefile.am | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) hooks/post-receive -- Olena, a generic and efficient image processing platform