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 unstable/scribo has been updated discards a6a7616f0ac2af8f18383c5defceb00dd84f10b5 (commit) discards d118d1bda852b2d111f597441a175d669776167c (commit) via 720b4ac09e8e1ce997da5f3a3055dd5e9506a310 (commit) via d76275d6454849a89f1a8e443856b39ddb889efd (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 (a6a7616f0ac2af8f18383c5defceb00dd84f10b5) \ N -- N -- N (720b4ac09e8e1ce997da5f3a3055dd5e9506a310)

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 ----------------------------------------------------------------- 720b4ac doc/Doxyfile.in: Disable QCH file generation. d76275d mln/linear/.#ch_convolve.hh: Remove. -----------------------------------------------------------------------

Summary of changes: milena/ChangeLog | 4 ---- 1 files changed, 0 insertions(+), 4 deletions(-)

hooks/post-receive