Clearly the number of changes involved in renaming AGREEMENT to AGREE and INVALIDATE to REVOKE was overwhelming and made the document difficult to read. I've removed all of those changes and attached another draft which should be much simpler to parse.<div>
<br></div><div>Wesley<br><br><div class="gmail_quote">On Tue, May 8, 2012 at 3:56 PM, Wesley Bland <span dir="ltr"><<a href="mailto:email@example.com" target="_blank">firstname.lastname@example.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
We've completed the new draft of the FT chapter. I've attached just the FT chapter to this email. The rest of the document can be found on the ticket (<a href="https://svn.mpi-forum.org/trac/mpi-forum-web/ticket/323" target="_blank">https://svn.mpi-forum.org/trac/mpi-forum-web/ticket/323</a>).
<div><br></div><div>In this new version, we've clarified many of the points raised at the forum meetings and on the recent conference calls. Here's a list:</div><div><br></div><div>- MPI_COMM_INVALIDATE is now MPI_COMM_REVOKE due to naming conflicts (along with the RMA and I/O versions)</div>
<div>- MPI_COMM_AGREEMENT is now MPI_COMM_AGREE to follow naming conventions</div><div>- A paragraph was added to 17.1 (Introduction) to clarify that FT is optional, but implementing the new FT functions is not.</div><div>
- Section 17.2.2 (Point-to-Point and Collective Communication) has been reworked to try to make it more clean when to return MPI_ERR_PENDING and MPI_ERR_PROC_FAILED.</div><div>- The non-rooted collective discussion in the advice to users in Section 17.2.2 has been changed to make it more clear when collective operations might have non-uniform return values.</div>
<div>- The definition of MPI_COMM_REVOKE has been clarified to further define that the function is not collective and does not have a matching call on remote processes.</div><div><br></div><div>If you see more changes that you think would be helpful, please let us know either on this list or on the conference call tomorrow.</div>