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 exp/newdoc has been updated
discards 53d161004998be99b1fdd1ea0b9c9628f9ff96fe (commit)
via f4024c0f648bac243f0cb60c04ae3e895a9e08d3 (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 (53d161004998be99b1fdd1ea0b9c9628f9ff96fe)
\
N -- N -- N (f4024c0f648bac243f0cb60c04ae3e895a9e08d3)
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 -----------------------------------------------------------------
f4024c0 doc/mln/labeling/labeling.dox: Write general documentation on labeling.
-----------------------------------------------------------------------
Summary of changes:
milena/doc/mln/labeling/labeling.dox | 24 ++++++++++++++----------
1 files changed, 14 insertions(+), 10 deletions(-)
hooks/post-receive
--
Olena, a generic and efficient image processing platform
Show replies by date