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> 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 > <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
