Ok. If it contains everything you put on the original topo-fixes (and topo-fixes-fixed), I might as well kill those two repos and put your repo URL on the ticket.
So -- before I whack those two -- can you absolutely confirm that you've got everything from the topo-fixes-fixed repo? IIRC, there was some other fixes/updates to the topo base in there, not just the new dist_graph improvements. On Jan 18, 2013, at 11:06 AM, George Bosilca <bosi...@icl.utk.edu> wrote: > It's a fork from the official ompi (well the hg version of it). We will push > back once we're done. > > George. > > On Jan 18, 2013, at 15:42 , "Jeff Squyres (jsquyres)" <jsquy...@cisco.com> > wrote: > >> George -- >> >> Should I pull from your repo into >> https://bitbucket.org/jsquyres/ompi-topo-fixes-fixed? Or did you >> effectively fork, and you guys will put back to SVN when you're done? >> >> >> On Jan 18, 2013, at 5:47 AM, George Bosilca <bosi...@icl.utk.edu> >> wrote: >> >>> Takahiro, >>> >>> The MPI_Dist_graph effort is happening in >>> ssh://h...@bitbucket.org/bosilca/ompi-topo. I would definitely be >>> interested in seeing some test cases, and giving this branch a tough test. >>> >>> George. >>> >>> On Jan 18, 2013, at 02:43 , "Kawashima, Takahiro" >>> <t-kawash...@jp.fujitsu.com> wrote: >>> >>>> Hi, >>>> >>>> Fujitsu is interested in completing MPI-2.2 on Open MPI and Open MPI >>>> -based Fujitsu MPI. >>>> >>>> We've read wiki and tickets. These two tickets seem to be almost done >>>> but need testing and bug fixing. >>>> >>>> https://svn.open-mpi.org/trac/ompi/ticket/2223 >>>> MPI-2.2: MPI_Dist_graph_* functions missing >>>> >>>> https://svn.open-mpi.org/trac/ompi/ticket/3127 >>>> MPI-2.2: Add reduction support for MPI_C_*COMPLEX and MPI::*COMPLEX >>>> >>>> My colleagues are planning to work on these. They will write test codes >>>> and try to fix bugs. Test codes and patches can be contributed to the >>>> community. If they cannot fix some bugs, we will report details. They >>>> are planning to complete them in around March. >>>> >>>> With that two questions. >>>> >>>> The latest statuses written in these ticket comments are correct? >>>> Is there any more progress? >>>> >>>> Where are the latest codes? >>>> In ticket #2223 says it is on Jeff's ompi-topo-fixes bitbucket branch. >>>> https://bitbucket.org/jsquyres/ompi-topo-fixes >>>> But Jeff seems to have one more branch with a similar name. >>>> https://bitbucket.org/jsquyres/ompi-topo-fixes-fixed >>>> Ticket #3127 says it is on Jeff's mpi22-c-complex bitbucket branch. >>>> But there is no such branch now. >>>> https://bitbucket.org/jsquyres/mpi22-c-complex >>>> >>>> Best regards, >>>> Takahiro Kawashima, >>>> MPI development team, >>>> Fujitsu >>>> _______________________________________________ >>>> devel mailing list >>>> de...@open-mpi.org >>>> http://www.open-mpi.org/mailman/listinfo.cgi/devel >>> >>> >>> _______________________________________________ >>> devel mailing list >>> de...@open-mpi.org >>> http://www.open-mpi.org/mailman/listinfo.cgi/devel >> >> >> -- >> Jeff Squyres >> jsquy...@cisco.com >> For corporate legal information go to: >> http://www.cisco.com/web/about/doing_business/legal/cri/ >> >> >> _______________________________________________ >> devel mailing list >> de...@open-mpi.org >> http://www.open-mpi.org/mailman/listinfo.cgi/devel > > > _______________________________________________ > devel mailing list > de...@open-mpi.org > http://www.open-mpi.org/mailman/listinfo.cgi/devel -- Jeff Squyres jsquy...@cisco.com For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/
