You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@reef.apache.org by Saikat Kanjilal <sx...@gmail.com> on 2017/05/03 14:56:17 UTC

reef-1584

@Markus et al,
I was re-starting the efforts to work on this JIRA yesterday and noticed
that none of the projects in VS have been upgraded to .Net Framework 4.5.1
in my version of master which is downstream from apache master, are we sure
that my change doing this upgrade for all projects actually went in
actually went into master, I was quite surprised to find this.  I believe
the JIRA to do this work was here:
https://issues.apache.org/jira/browse/REEF-1583


Let me know what I may be missing here.
Thanks

RE: reef-1584

Posted by Mariia Mykhailova <ma...@microsoft.com.INVALID>.
Git fetch just fetches the data about the upstream repo, It doesn't update the state of your branch. You have to follow it with "git merge upstream/master" for your current branch to be merged with that branch of upstream

-Mariia

-----Original Message-----
From: Saikat Kanjilal [mailto:sxk1969@gmail.com] 
Sent: Wednesday, May 3, 2017 11:00 AM
To: dev@reef.apache.org
Subject: Re: reef-1584

Thanks Mariia, I did a git fetch upstream which should have synched my clone with the apache master repo I didnt see any changes come through, this is why I was asking, I will keep digging into this and see if there are other issues with my environment.

On Wed, May 3, 2017 at 10:50 AM, Mariia Mykhailova < mamykhai@microsoft.com.invalid> wrote:

> Pull request 1277 which claims to resolve this JIRA is there in 
> apache/reef as commit b4c379c
>
> Check that your clone of apache/reef (skanjila/reef) is synced with 
> master repo; I don't see your local state of enlistment but
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithu
> b.com%2Fskanjila%2Freef&data=02%7C01%7Cmamykhai%40microsoft.com%7Cc444
> c30f58e242a14f9208d4924e4b10%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C
> 0%7C636294312341198115&sdata=4GUENiKpCWY2RpmgT3MPWjN4BbZ5TH69iTktJh%2F
> RkF8%3D&reserved=0 says it's 28 commits behind apache:master
>
> -Mariia
>
> -----Original Message-----
> From: Saikat Kanjilal [mailto:sxk1969@gmail.com]
> Sent: Wednesday, May 3, 2017 7:56 AM
> To: dev@reef.apache.org
> Subject: reef-1584
>
> @Markus et al,
> I was re-starting the efforts to work on this JIRA yesterday and 
> noticed that none of the projects in VS have been upgraded to .Net 
> Framework 4.5.1 in my version of master which is downstream from 
> apache master, are we sure that my change doing this upgrade for all 
> projects actually went in actually went into master, I was quite 
> surprised to find this.  I believe the JIRA to do this work was here:
> https://na01.safelinks.protection.outlook.com/?url=
> https%3A%2F%2Fissues.apache.org%2Fjira%2Fbrowse%2FREEF-
> 1583&data=02%7C01%7Cmamykhai%40microsoft.com%
> 7Ce410020223534ef6abc208d492349183%7C72f988bf86f141af91ab2d7cd011
> db47%7C1%7C0%7C636294201854355799&sdata=0xiz0N1pq5ChDuC1natLWobgVjOBfq
> 0JGZHki8%2FZ2ms%3D&reserved=0
>
>
> Let me know what I may be missing here.
> Thanks
>

Re: reef-1584

Posted by Saikat Kanjilal <sx...@gmail.com>.
Thanks Mariia, I did a git fetch upstream which should have synched my
clone with the apache master repo I didnt see any changes come through,
this is why I was asking, I will keep digging into this and see if there
are other issues with my environment.

On Wed, May 3, 2017 at 10:50 AM, Mariia Mykhailova <
mamykhai@microsoft.com.invalid> wrote:

> Pull request 1277 which claims to resolve this JIRA is there in
> apache/reef as commit b4c379c
>
> Check that your clone of apache/reef (skanjila/reef) is synced with master
> repo; I don't see your local state of enlistment but
> https://github.com/skanjila/reef says it's 28 commits behind apache:master
>
> -Mariia
>
> -----Original Message-----
> From: Saikat Kanjilal [mailto:sxk1969@gmail.com]
> Sent: Wednesday, May 3, 2017 7:56 AM
> To: dev@reef.apache.org
> Subject: reef-1584
>
> @Markus et al,
> I was re-starting the efforts to work on this JIRA yesterday and noticed
> that none of the projects in VS have been upgraded to .Net Framework 4.5.1
> in my version of master which is downstream from apache master, are we sure
> that my change doing this upgrade for all projects actually went in
> actually went into master, I was quite surprised to find this.  I believe
> the JIRA to do this work was here:
> https://na01.safelinks.protection.outlook.com/?url=
> https%3A%2F%2Fissues.apache.org%2Fjira%2Fbrowse%2FREEF-
> 1583&data=02%7C01%7Cmamykhai%40microsoft.com%
> 7Ce410020223534ef6abc208d492349183%7C72f988bf86f141af91ab2d7cd011
> db47%7C1%7C0%7C636294201854355799&sdata=0xiz0N1pq5ChDuC1natLWobgVjOBfq
> 0JGZHki8%2FZ2ms%3D&reserved=0
>
>
> Let me know what I may be missing here.
> Thanks
>

RE: reef-1584

Posted by Mariia Mykhailova <ma...@microsoft.com.INVALID>.
Pull request 1277 which claims to resolve this JIRA is there in apache/reef as commit b4c379c

Check that your clone of apache/reef (skanjila/reef) is synced with master repo; I don't see your local state of enlistment but https://github.com/skanjila/reef says it's 28 commits behind apache:master

-Mariia

-----Original Message-----
From: Saikat Kanjilal [mailto:sxk1969@gmail.com] 
Sent: Wednesday, May 3, 2017 7:56 AM
To: dev@reef.apache.org
Subject: reef-1584

@Markus et al,
I was re-starting the efforts to work on this JIRA yesterday and noticed that none of the projects in VS have been upgraded to .Net Framework 4.5.1 in my version of master which is downstream from apache master, are we sure that my change doing this upgrade for all projects actually went in actually went into master, I was quite surprised to find this.  I believe the JIRA to do this work was here:
https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fissues.apache.org%2Fjira%2Fbrowse%2FREEF-1583&data=02%7C01%7Cmamykhai%40microsoft.com%7Ce410020223534ef6abc208d492349183%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636294201854355799&sdata=0xiz0N1pq5ChDuC1natLWobgVjOBfq0JGZHki8%2FZ2ms%3D&reserved=0


Let me know what I may be missing here.
Thanks