Well.. That's a very good reason.
FWIW, I am not allowed to perform those merges and do not feel confident
enough in the testing process to take that in charge in the short term.
Plus there is a bug when mixing intel mpi and b2 that makes automatic
testing unsafe on my platform. But I'd be interested in helping in the
future.
Alain
On 17/03/2015 16:19, Matthias Troyer wrote:
The only reason that keeps me from doing that is problems at work after the SNB
dropped the cap on the Swiss Franc that keep me stuck on administrative issues
and making sure that I have sufficient funding for my research group that
suddenly became much more expensive. Would someone else be able to merge the
important patches?
Matthias
On Mar 17, 2015, at 16:14, Alain Miniussi <alain.miniu...@oca.eu> wrote:
Hi,
Has the 1.58 is about to roll, I expected to see a few fixes in it that already
missed the 1.57.
https://github.com/boostorg/mpi/compare/master...develop?diff=split&name=develop
That concerns some quite trivial fixes that have not been triggering
regressions as far as I know like:
https://github.com/boostorg/mpi/commit/34c546b9cd61e075dfabef2846d5e2f0907e7b17
and bugfixes like:
https://github.com/boostorg/mpi/commit/6c597245a2f72e861781c38bc53b68be3c83d5f5
(which otherwise hangs with intel MPI)
Even doc bug fixes seems to be blocked on develop.
https://github.com/boostorg/mpi/commit/33924337320fad6a52ff6aa84cb88eacbddadb94
Is there a reason to keep those away from master ?
Regards
Alain
_______________________________________________
Boost-mpi mailing list
Boost-mpi@lists.boost.org
http://lists.boost.org/mailman/listinfo.cgi/boost-mpi
_______________________________________________
Boost-mpi mailing list
Boost-mpi@lists.boost.org
http://lists.boost.org/mailman/listinfo.cgi/boost-mpi
--
---
Alain
_______________________________________________
Boost-mpi mailing list
Boost-mpi@lists.boost.org
http://lists.boost.org/mailman/listinfo.cgi/boost-mpi
