Per the Tuesday teleconf, DongInn and I revamped the svn-post-commit hook
script a bit this week. The wiki shows all the info you need:
https://svn.open-mpi.org/trac/ompi/wiki/TracSVNCommitMessages
Short version:
1. "cmr" commands must now be on a line by themselves
2. the cmr commands are
On 7/19/13 10:58 AM, "George Bosilca" wrote:
>1. The BML endpoint structure (aka. BML proc) is well known and defined
>in the bml.h. So it is not technically opaque
It's opaque in that outside of the R2 BML, users were not supposed to poke
at what's in proc_bml without using the BML interface.
Brian,
I have few questions/comments about the proposed approach:
1. The BML endpoint structure (aka. BML proc) is well known and defined in the
bml.h. So it is not technically opaque…
2. When allocating an ompi_proc_t structure you will always have to allocate
for an array large enough to con
I've now talked to both George and Nathan. Let me summarize for the web
archives / community:
1. There are two main points of contention:
1a. ompi_info has a *very long-standing precedent* behavior of using
MCA params to exclude the display of components (and their params).
Users have com
George and I talked about this on the phone; I understand his questions better
now.
Nathan and I will get together and work through his questions and come back to
everyone with some answers / proposals.
On Jul 19, 2013, at 9:27 AM, George Bosilca wrote:
>
> My point is the following. I favo
My point is the following. I favor consistent behaviors and I'm always in favor
of respecting the configuration files. ALWAYS like in the word that mean all
cases without exception. Thus, by default, ompi_info as any other component of
the Open MPI infrastructure MUST read the configuration fil
