I just updated the wiki: NOTE: Pull requests on ompi-release must include a hash reference in the body/comments corresponding to the commit(s) on ompi:master from which it is derived, OR indicate that this is solely a release branch bug (i.e., there's no corresponding commit on ompi:master because the bug doesn't/didn't exist on ompi:master).
On Oct 27, 2014, at 9:57 PM, Ralph Castain <r...@open-mpi.org<mailto:r...@open-mpi.org>> wrote: Just create a topic branch from v1.8 in a local clone of ompi-release, make the change there, and then file a PR on the ompi-release repo Obviously, if it is a bug solely confined to v1.8, you can’t put it in master first :-) On Oct 27, 2014, at 3:22 PM, Howard Pritchard <hpprit...@gmail.com<mailto:hpprit...@gmail.com>> wrote: Hi Folks, A cut and past error seems to have happened with plm_alps_modules.c in 1.8 which causes a compile failure when building for cray. So right now, there's no building ompi 1.8 for crays. The problem is not present in master. For these kinds of problems, are we suppose to bypass all the "has to be in master, need commit, etc." stuff described in https://github.com/open-mpi/ompi/wiki/SubmittingPullRequests and just go straight to pushing to a fork of ompi-release, etc. as per the rest of the instructions on submitting pull requests? Just want to make sure I'm doing the right thing here. Howard _______________________________________________ devel mailing list de...@open-mpi.org Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/devel Link to this post: http://www.open-mpi.org/community/lists/devel/2014/10/16104.php _______________________________________________ devel mailing list de...@open-mpi.org<mailto:de...@open-mpi.org> Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/devel Link to this post: http://www.open-mpi.org/community/lists/devel/2014/10/16105.php -- Jeff Squyres jsquy...@cisco.com<mailto:jsquy...@cisco.com> For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/
