<p>Yes. That's just a problem because the size of the edit is so large. Once the ticket0 changes go away it looks fine. Unfortunately there's not a lot I can do to fix that at the moment.</p>
<p>Wesley</p>
<div class="gmail_quote">On May 10, 2012 11:15 AM, "Supalov, Alexander" <<a href="mailto:alexander.supalov@intel.com">alexander.supalov@intel.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div lang="EN-US" link="blue" vlink="purple">
<div>
<p class="MsoNormal"><span lang="DE" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Hi Bland,<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="DE" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Thanks. It appears that table 17.1 between pages 545 and 546 ran away from Section 17.4 where there’s a colon awaiting it. LaTeX, I suppose.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Best regards.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Alexander<u></u><u></u></span></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> <a href="mailto:mpi3-ft-bounces@lists.mpi-forum.org" target="_blank">mpi3-ft-bounces@lists.mpi-forum.org</a> [mailto:<a href="mailto:mpi3-ft-bounces@lists.mpi-forum.org" target="_blank">mpi3-ft-bounces@lists.mpi-forum.org</a>]
<b>On Behalf Of </b>Wesley Bland<br>
<b>Sent:</b> Wednesday, May 09, 2012 3:20 PM<br>
<b>To:</b> <a href="mailto:mpi3-ft@lists.mpi-forum.org" target="_blank">mpi3-ft@lists.mpi-forum.org</a><br>
<b>Subject:</b> Re: [Mpi3-ft] Updated FT Chapter<u></u><u></u></span></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">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.<u></u><u></u></p>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt">Wesley<u></u><u></u></p>
<div>
<p class="MsoNormal">On Tue, May 8, 2012 at 3:56 PM, Wesley Bland <<a href="mailto:wbland@eecs.utk.edu" target="_blank">wbland@eecs.utk.edu</a>> wrote:<u></u><u></u></p>
<p class="MsoNormal">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>).
<u></u><u></u></p>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">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:<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">- MPI_COMM_INVALIDATE is now MPI_COMM_REVOKE due to naming conflicts (along with the RMA and I/O versions)<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">- MPI_COMM_AGREEMENT is now MPI_COMM_AGREE to follow naming conventions<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">- A paragraph was added to 17.1 (Introduction) to clarify that FT is optional, but implementing the new FT functions is not.<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">- 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.<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">- 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.<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">- 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.<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">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.<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">Thanks,<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">Wesley Bland<u></u><u></u></p>
</div>
</div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
</div>
<font face="monospace">--------------------------------------------------------------------------------------<br>
Intel GmbH<br>
Dornacher Strasse 1<br>
85622 Feldkirchen/Muenchen, Deutschland <br>
Sitz der Gesellschaft: Feldkirchen bei Muenchen<br>
Geschaeftsfuehrer: Douglas Lusk, Peter Gleissner, Hannes Schwaderer<br>
Registergericht: Muenchen HRB 47456 <br>
Ust.-IdNr./VAT Registration No.: DE129385895<br>
Citibank Frankfurt a.M. (BLZ 502 109 00) 600119052</font></div>
<br>_______________________________________________<br>
mpi3-ft mailing list<br>
<a href="mailto:mpi3-ft@lists.mpi-forum.org">mpi3-ft@lists.mpi-forum.org</a><br>
<a href="http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi3-ft" target="_blank">http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi3-ft</a><br></blockquote></div>