[OMPI devel] Annual Git committers audit
It's that time of year again! It's that time when we audit who has commit access to the Open MPI repos, and remove those who are no longer relevant, those who have moved to other jobs, and/or are otherwise not actively committing code to Open MPI. * *** PLEASE COMPLETE THIS BY NEXT TUESDAY, 23 AUG 2016 *** * On this spreadsheet: https://docs.google.com/spreadsheets/d/1QNR0M46pwgauydTKPx5PqmQX30GFCq9dAkoUwQV_op8/edit?usp=sharing For each person in your organization: 1. If the person has commit access to a given repo, a group name will appear in the first column. Your job is to put an "x" in the second column if they *still need* commit access to that repo. 2. Mark the background color of each person as: - Green: if the person still needs commit access *at all* - Red: if the person does not need any commit access (#2 lets us know that you have evaluated each person / you have completed this audit) Remember: *anyone* can submit pull requests, even if they don't have commit access. So it's ok to have a small number of people in an organization with commit access, even if you have a larger number of people in that organization who are creating pull requests. -- Jeff Squyres jsquy...@cisco.com For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/ ___ devel mailing list devel@lists.open-mpi.org https://rfd.newmexicoconsortium.org/mailman/listinfo/devel
[OMPI devel] about MPI_Reduce_local
Folks, when reading the dev meeting minutes, i saw MPI_Reduce_local was discussed and might be moved to the coll framework, and here are my 0.02 US$ : the prototype of MPI_Reduce_local is int MPI_Reduce_local(const void *inbuf, void *inoutbuf, int count, MPI_Datatype datatype, MPI_Op op) bottom line, this is not a collective operation, so that could explain why it is not part of the coll framework. Cheers, Gilles ___ devel mailing list devel@lists.open-mpi.org https://rfd.newmexicoconsortium.org/mailman/listinfo/devel
