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/deb-packages has been updated
discards faaecfd2d463729324c7aa4e69643463938c509d (commit)
discards f51e0526ea66999a00f9f6281a82fecd8dfed9b3 (commit)
discards abcd89d3fb4463d4fdd5f31a06552f8107e367c6 (commit)
discards a84e5122a3538c77efe52029a2609f36e273a6d7 (commit)
discards bce58971a038ba44669597cabfb8e95886411b34 (commit)
via 07dea83cb87e65be67e7fa5f5d7e280b024416d8 (commit)
via 1c20ebd37e9918e623d21217823906df1a60da38 (commit)
via 63beebcf5d6f9c9de39ff24dbb7d5d990d9f32ae (commit)
via ee9f7de75ef0c03cce72d235596c7df86b5c5d3b (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 (faaecfd2d463729324c7aa4e69643463938c509d)
\
N -- N -- N (07dea83cb87e65be67e7fa5f5d7e280b024416d8)
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 -----------------------------------------------------------------
07dea83 debian/olena-bin.install: Add shared files in olena-bin.
1c20ebd Fix access to xsl templates.
63beebc debian/changelog: Change distribution.
ee9f7de demo/viewer/runner.cc: Fix libexec path.
-----------------------------------------------------------------------
Summary of changes:
ChangeLog | 4 ----
debian/source/options | 4 ++--
2 files changed, 2 insertions(+), 6 deletions(-)
hooks/post-receive
--
Olena, a generic and efficient image processing platform