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 swilena has been updated discards 37cae442b0c2ac00304889d5c66f260314ad76b9 (commit) discards 0e1c12bf83184fd2a0c84455463be7d9633f5467 (commit) via 17105bad97c497797a9f5ac257aca1b25c9a3678 (commit) via 1c93a61f5b62f6ca9d96b8349d5140874adc0bce (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 (37cae442b0c2ac00304889d5c66f260314ad76b9) \ N -- N -- N (17105bad97c497797a9f5ac257aca1b25c9a3678) 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 ----------------------------------------------------------------- 17105ba Adjust Swilena to Automake parallel tests. 1c93a61 Enable verbose messages in Swilena Python tests. ----------------------------------------------------------------------- Summary of changes: swilena/ChangeLog | 1 + swilena/run.in | 4 ++-- 2 files changed, 3 insertions(+), 2 deletions(-) hooks/post-receive -- Olena, a generic and efficient image processing platform