Open MPI logo

Open MPI Development Mailing List Archives

  |   Home   |   Support   |   FAQ   |   all Development mailing list

Subject: Re: [OMPI devel] [EXTERNAL] Re: SHMEM v1.7 merge proposal
From: Barrett, Brian W (bwbarre_at_[hidden])
Date: 2013-10-29 09:21:12


1) thanks for jumping in before I woke up
2) y'all? You've been in Kentucky too long :)

Brian



Sent with Good (www.good.com)


-----Original Message-----
From: Jeff Squyres (jsquyres) [jsquyres_at_[hidden]<mailto:jsquyres_at_[hidden]>]
Sent: Tuesday, October 29, 2013 05:17 AM Mountain Standard Time
To: Open MPI Developers
Subject: [EXTERNAL] Re: [OMPI devel] SHMEM v1.7 merge proposal

I'm not sure what you mean.

Brian's proposal was that y'all the shmem stuff go into a single SVN branch off the v1.7 branch. This way, it can be reviewed properly and easily merged into the actual v1.7 SVN branch.

Sent from my phone. No type good.
On Oct 29, 2013, at 7:09 AM, "Mike Dubman" <miked_at_[hidden]<mailto:miked_at_[hidden]>> wrote:

will it be ok, that once all is ready, we push git2svn branch for this?


On Tue, Oct 29, 2013 at 12:35 PM, Jeff Squyres (jsquyres) <jsquyres_at_[hidden]<mailto:jsquyres_at_[hidden]>> wrote:
I think Brian's point is that it should be a SVN branch.


On Oct 29, 2013, at 3:27 AM, Mike Dubman <miked_at_[hidden]<mailto:miked_at_[hidden]>> wrote:

> Hi,
> This is exactly the way we handle it now. We have internal branch on top of v1.7 with all SHMEM code in it.
> It runs mtt and other tests.
>
> Once we done with all changes - we will provide patch (and branch direct access if needed) for GK.
>
> Kind Regards
> Mike.
>
>
> On Tue, Oct 29, 2013 at 1:02 AM, Barrett, Brian W <bwbarre_at_[hidden]<mailto:bwbarre_at_[hidden]>> wrote:
> All -
>
> Ralph and I talked today about the logistics of bringing the OpenSHMEM
> code to the 1.7 release branch, as it's now a fairly large set of changes
> from the trunk. What we propose is to follow the same proceedure we used
> when merging in the RTE framework change, which is essentially a staging
> branch. So, Mellanox (as the one filing the CMR) would branch from 1.7,
> bring the OpenSHMEM changes into that (and hopefully test), and then file
> a single CMR for the changes from the branch. If done properly, the GK
> then only has to merge with --reintegrate and we're set.
>
> Let's talk about it on the call tomorrow, but that's the current proposal.
>
> Brian
>
> --
> Brian W. Barrett
> Scalable System Software Group
> Sandia National Laboratories
>
>
>
>
> _______________________________________________
> devel mailing list
> devel_at_[hidden]<mailto:devel_at_[hidden]>
> http://www.open-mpi.org/mailman/listinfo.cgi/devel
>
> _______________________________________________
> devel mailing list
> devel_at_[hidden]<mailto:devel_at_[hidden]>
> http://www.open-mpi.org/mailman/listinfo.cgi/devel


--
Jeff Squyres
jsquyres_at_[hidden]<mailto:jsquyres_at_[hidden]>
For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/

_______________________________________________
devel mailing list
devel_at_[hidden]<mailto:devel_at_[hidden]>
http://www.open-mpi.org/mailman/listinfo.cgi/devel

_______________________________________________
devel mailing list
devel_at_[hidden]<mailto:devel_at_[hidden]>
http://www.open-mpi.org/mailman/listinfo.cgi/devel