Re: [OMPI devel] fixing a bug in 1.8 that's not in master

2014-10-28 Thread Jeff Squyres (jsquyres)
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

Re: [OMPI devel] fixing a bug in 1.8 that's not in master

2014-10-27 Thread Ralph Castain
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

[OMPI devel] fixing a bug in 1.8 that's not in master

2014-10-27 Thread Howard Pritchard
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