3 May
2012
3 May
'12
6:08 p.m.
On 17/04/2012 14:50, git(a)lrde.epita.fr wrote:
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 master has been updated
via b9968d11b67e760f73bb5a3ef5278f994f509a7f (commit)
via cd24fef1af613a4f8d79161ff0d74e3d8cd8f6f0 (commit)
from dd67b61c24dfbce6a081a8831ac9d15e6d46fdce (commit)
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 -----------------------------------------------------------------
b9968d1 Disable postcondition on neighborhood.
cd24fef Add implicit conversion between types of different quantizations. i.e
rgb<n> => rgb<m>, int_u<n> => int_u<m>...
-----------------------------------------------------------------------
Summary of changes:
milena/mln/algebra/vec.hh | 11 +++++++++++
milena/mln/core/alias/neighb2d.hh | 2 +-
milena/mln/value/int_u.hh | 15 +++++++++++++++
milena/mln/value/rgb.hh | 27 +++++++++++++++++++++++++--
4 files changed, 52 insertions(+), 3 deletions(-)
Sorry, but I had to revert these changes (i.e., set back `master' two
commits before). The current policy in Olena is not to send patches to
the branch `master' (nor `next') directly, but to a feature branch,
which will eventually be merged with `next' and then with `master'
during the integration and release processes.
Moreover, your changes do not include a proper ChangeLog entry (although
your Git messages seem OK). As long as we do not have a policy
regarding the automation of ChangeLog generation, filling ChangeLog
files is still mandatory in the Olena project. (This will evolve in the
future to, as maintaining ChangeLogs by hand is counter-productive with
Git).
I have moved your changes into another branch named `edwin'. Feel free
to rename it if you want.