[Mpi-forum] First reading: MPI_Count
Barrett, Brian W
bwbarre at sandia.gov
Mon Mar 14 17:54:56 CDT 2011
That makes sense, although it seems like once a ticket has been merged
into /approved, it should no longer have it's ticket macros enabled to
highlight the changes. I'm not sure whether they should still be marked
up in the latex; that seems like an unsustainable path forward, but I have
no strong feelings against it.
On 3/14/11 3:26 PM, "Jeff Squyres" <jsquyres at cisco.com> wrote:
>Actually, I just checked. Dave copied the latex from the latest
>/approved HEAD -- meaning that all those markups for old tickets are
>(see http://lists.mpi-forum.org/mpi-forum/2011/01/0884.php for an
>explanation of our SVN -- I had to find this earlier today so that I
>could remember where things were in SVN :-) )
>Search for "ticket265" and "ticket269" to find all the changes.
>There's a bunch of places where the coloring mis-behaved, too. So trust
>the "ticket265" and "ticket269" annotations more than the colors. :-(
>On Mar 14, 2011, at 5:20 PM, Jeff Squyres wrote:
>> On Mar 14, 2011, at 5:14 PM, Barrett, Brian W wrote:
>>> Why do both documents have both the changes proposed and the
>>> collectives both marked as changes? It makes it a tad bit harder to
>>> determine where there are changes to the document for each proposal :).
>> Dave (Solt) copied from /approved.
>> I wonder if he copied from a while ago, though...
>> Jeff Squyres
>> jsquyres at cisco.com
>> For corporate legal information go to:
>> mpi-forum mailing list
>> mpi-forum at lists.mpi-forum.org
>jsquyres at cisco.com
>For corporate legal information go to:
>mpi-forum mailing list
>mpi-forum at lists.mpi-forum.org
Brian W. Barrett
Dept. 1423: Scalable System Software
Sandia National Laboratories
More information about the mpi-forum