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. Brian On 3/14/11 3:26 PM, "Jeff Squyres" <[email protected]> wrote:
Actually, I just checked. Dave copied the latex from the latest /approved HEAD -- meaning that all those markups for old tickets are still there.
(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 non-blocking 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 [email protected] For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/
_______________________________________________ mpi-forum mailing list [email protected] http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi-forum
-- Jeff Squyres [email protected] For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/
_______________________________________________ mpi-forum mailing list [email protected] http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi-forum
-- Brian W. Barrett Dept. 1423: Scalable System Software Sandia National Laboratories