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 fft has been updated discards 773114f96eeb083d260eed6e5a508d9b93d9c9b2 (commit) via 0a078938b8f3fdc10d234fe663ff74a4b6a44284 (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 (773114f96eeb083d260eed6e5a508d9b93d9c9b2) \ N -- N -- N (0a078938b8f3fdc10d234fe663ff74a4b6a44284) 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 ----------------------------------------------------------------- 0a07893 Run FFT unit tests only when FFTW3 support is enabled. ----------------------------------------------------------------------- Summary of changes: milena/tests/unit_test/cond_tests_fftw3 | 1 + 1 file changed, 1 insertion(+) create mode 100644 milena/tests/unit_test/cond_tests_fftw3 hooks/post-receive -- Olena, a generic and efficient image processing platform