We probably will generate single patch with all changes applied in v1.7 for
shmem and create svn branch from 1.7 + patch.
Im sorry, did not mean we port git history from git to svn, it sounds
trouble.
Mike,
I've never personally used git2svn, but my understanding is that it would
require us to es
As I understood it, they would create a new 1.7 branch and use git2svn to merge
into it - i.e., there would be a new 1.7 branch that had their changes in it.
The GK could then use "reintegrate" to bring those changes into the official
1.7 branch.
On Oct 29, 2013, at 7:41 AM, Dave Goodell (dgoo
Mike,
I've never personally used git2svn, but my understanding is that it would
require us to essentially "lock" the repository to all other commits while you
are using it, which isn't very friendly to the rest of the community. Also,
using git2svn probably wouldn't twiddle the SVN merge track
I wondered where that was coming from.
-Original Message-
From: devel [mailto:devel-boun...@open-mpi.org] On Behalf Of Jeff Squyres
(jsquyres)
Sent: Tuesday, October 29, 2013 7:53 AM
To: Open MPI Developers
Subject: Re: [OMPI devel] SHMEM v1.7 merge proposal
On Oct 29, 2013, at 7:16 AM
On Oct 29, 2013, at 7:16 AM, "Jeff Squyres (jsquyres)"
wrote:
> ...that y'all the shmem stuff...
I guess this is what happens when you buy an iPhone in Kentucky.
DYAC!
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/leg
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"
mai
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) <
jsquy...@cisco.com> wrote:
> I think Brian's point is that it should be a SVN branch.
>
>
> On Oct 29, 2013, at 3:27 AM, Mike Dubman wrote:
>
> > Hi,
> > This is e
I think Brian's point is that it should be a SVN branch.
On Oct 29, 2013, at 3:27 AM, Mike Dubman 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
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, Bar
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
10 matches
Mail list logo
