[mpiwg-tools] Tools WG webex tomorrow!
Jeff Squyres (jsquyres)
jsquyres at cisco.com
Mon Aug 26 15:25:55 CDT 2013
On Aug 26, 2013, at 12:44 PM, Kathryn Mohror <kathryn at llnl.gov> wrote:
> Hello everybody and Happy Monday!
>
> Please take a look at these tickets because we need to publish the final drafts *tomorrow* if they will be read in Madrid.
>
> I updated 377 and 378 based on our conversations in the last call, so make sure that you like them and speak up if you don't.
Oy, you're going to kill me, but for 377:
"...because the tool won’t have to iterate..."
Do we use contractions in the standard? If not, you should probably change "won't" to "will not".
For 378:
"If any OUT parameter to MPI_T_CVAR_GET_INFO"
OUT is in the wrong font. Same for PVAR and CATEGORY.
> We didn't go over 385,
Rather than replace the whole paragraph, is it possible to just edit the specific words that are changing? It's somewhat difficult to read the two paragraphs and see exactly what changed...
(I know this is nit picky, but I'm going to be the one presenting this, and I'm sure someone is going to ask exactly what the difference is between the two :-) )
> 386,
What about MPI_T_PVAR_HANDLE_FREE? That takes a (session, handle) tuple, but doesn't have the text about MPI_T_ERR_INVALID_HANDLE.
Also for PVAR start, what if there are no handles associated with a session and MPI_T_PVAR_ALL_HANDLES is used? Do we return SUCCESS or ERR_PVAR_NO_STARTSTOP?
> and 387
Looks good. :-)
> due to lack of time (I blame Fortran!)
Long live Fortran 2028!
--
Jeff Squyres
jsquyres at cisco.com
For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/
More information about the mpiwg-tools
mailing list