[GitHub] ignite pull request #883: Ignite 1.6.3

2016-07-22 Thread asfgit
Github user asfgit closed the pull request at:

https://github.com/apache/ignite/pull/883


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[GitHub] ignite pull request #883: Ignite 1.6.3

2016-07-22 Thread ptupitsyn
GitHub user ptupitsyn opened a pull request:

https://github.com/apache/ignite/pull/883

Ignite 1.6.3



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/gridgain/apache-ignite ignite-1.6.3

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/883.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #883


commit 11c7e8fe53461f84924e5c29893865191f236c8c
Author: Anton Vinogradov 
Date:   2016-07-20T08:31:14Z

Documentation fix

commit 9b55658749d0e2a869bbb3614034d8aa1f0e95c1
Author: vozerov-gridgain 
Date:   2016-07-20T11:14:50Z

IGNITE-3405: IGFS: Restricted path modes interleaving, so that now only 
DUAL -> PRIMARY and DUAL -> PROXY paths are possible.

commit 6c5218f4d67c8e247f59dbe8deb58b51db2954a2
Author: vozerov-gridgain 
Date:   2016-07-20T11:15:11Z

Merge remote-tracking branch 'upstream/gridgain-7.6.2' into gridgain-7.6.2




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---