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 next has been updated
discards 19047401c5013ba8a930e9cd5a04301c9cd9064d (commit)
via df9e6b2880b4a1b75dca48155f3a1226fdca27a7 (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 (19047401c5013ba8a930e9cd5a04301c9cd9064d)
\
N -- N -- N (df9e6b2880b4a1b75dca48155f3a1226fdca27a7)
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 -----------------------------------------------------------------
df9e6b2 demo/xml2doc/main.cc: Add --template-path option.
-----------------------------------------------------------------------
Summary of changes:
scribo/ChangeLog | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
hooks/post-receive
--
Olena, a generic and efficient image processing platform
Show replies by date