Sounds good.
I can probably try to finish the patch in the next couple weeks, but
if someone needs it before I get a chance to look at it let me know.
Once the implementation is complete, then the RFC will be updated with
a termination date for further input.
Cheers,
Josh
On May 8,
On May 8, 2008, at 9:32 AM, Josh Hursey wrote:
I think 'all' would be a nice symmetric addition to complement 'none'
and then this would allow users to specify the "select best from all
available" option on the command line.
Ok, if you accept "all" and "none" as friendly ammendments to your
On May 8, 2008, at 8:15 AM, Jeff Squyres wrote:
On May 8, 2008, at 8:06 AM, Josh Hursey wrote:
--> If not intended to be used by users (i.e., it's an internal
mechanism only), is there a reason why we're not using a zero-length
string (e.g., mpirun --mca foo "")?
I think a zero length
On May 8, 2008, at 8:06 AM, Josh Hursey wrote:
--> If not intended to be used by users (i.e., it's an internal
mechanism only), is there a reason why we're not using a zero-length
string (e.g., mpirun --mca foo "")?
I think a zero length string might get confusing with the empty
string. The
On May 8, 2008, at 7:50 AM, Jeff Squyres wrote:
FWIW:
- I think "none" is a slightly better word than "null" for this value;
"none" implies that you don't open anything, whereas "null" could be a
specific component (as it is/was in some frameworks).
Calling it 'none' sounds fine to me.
-
FWIW:
- I think "none" is a slightly better word than "null" for this value;
"none" implies that you don't open anything, whereas "null" could be a
specific component (as it is/was in some frameworks).
- Whatever word we decide on will need to become a reserved component
name (i.e., no
What: Add a MCA-NULL option to open no components in mca_base_open()
Why: Sometimes we do not want to open or select any components of a
framework.
Where: patch attached for current trunk.
When: Needs further discussion.
Timeout: Unknown. [May 13, 2008 (After teleconf)?]
Short Version:
