[GitHub] ignite pull request #1013: IGNITE-3646 IGFS: Local secondary: Support symlin...

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

[GitHub] ignite pull request #1013: IGNITE-3646 IGFS: Local secondary: Support symlin...

andrey-kuznetsov
GitHub user tledkov-gridgain opened a pull request:

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

    IGNITE-3646 IGFS: Local secondary: Support symlinks for mkdirs operation.

   

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

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

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

    https://github.com/apache/ignite/pull/1013.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 #1013
   
----
commit dabd86c62e39eb983ef3d198c8b8ee96d2623c84
Author: Andrey Novikov <[hidden email]>
Date:   2016-08-31T09:00:19Z

    IGNITE-3811 Fixed query for merge with complex key on SQL Server.

commit 684f7af64169912959d1545990c736433494fa32
Author: tledkov-gridgain <[hidden email]>
Date:   2016-08-31T13:09:17Z

    IGNITE-3646 IGFS: Local secondary: Support symlinks for mkdirs operation.

----


---
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 [hidden email] or file a JIRA ticket
with INFRA.
---
Reply | Threaded
Open this post in threaded view
|

[GitHub] ignite pull request #1013: IGNITE-3646 IGFS: Local secondary: Support symlin...

andrey-kuznetsov
Github user asfgit closed the pull request at:

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


---
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 [hidden email] or file a JIRA ticket
with INFRA.
---