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 papers/lazzara.13.ijdar has been updated discards 15cdc8c98724c911d0c0f89ef77458faaa60733d (commit) discards 3e26b9e084823e5c169f53d684ab25dfd3dd3e26 (commit) discards a0864da5e298a1c5e268312c22bfff208cb7756f (commit) via b05f4e5c24d32b2d704badd28fd16dfa4a235bc6 (commit) via d437055460812dd65223c65cab4e7e5969a8abab (commit) via 54991acadad4a1bf95775f008523abae92be629b (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 (15cdc8c98724c911d0c0f89ef77458faaa60733d) \ N -- N -- N (b05f4e5c24d32b2d704badd28fd16dfa4a235bc6)

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 ----------------------------------------------------------------- b05f4e5 Use io::magick to save output. d437055 Fix binarization programs. 54991ac scribo/binarization/sauvola_ms.hh: Fix overlapping area criterion. -----------------------------------------------------------------------

Summary of changes:

hooks/post-receive