ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From ptupitsyn <...@git.apache.org>
Subject [GitHub] ignite pull request #1128: IGNITE-3995 .NET: Fix default cache name in ASP.N...
Date Wed, 28 Sep 2016 14:00:28 GMT
GitHub user ptupitsyn opened a pull request:


    IGNITE-3995 .NET: Fix default cache name in ASP.NET Session-State Store Provider


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

    $ git pull https://github.com/ptupitsyn/ignite ignite-3995

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


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

    This closes #1128
commit 53fbad7ddafdae7b368b0f207d06d16574978d62
Author: AKuznetsov <akuznetsov@gridgain.com>
Date:   2016-09-28T10:24:56Z

    Merge branch ignite-1.6.9 into ignite-1.7.2.

commit 4ff19c20b169e0373eafc8025a838db8bfc61f27
Author: sboikov <sboikov@gridgain.com>
Date:   2016-09-28T10:47:51Z

    ignite-3621 Fixed 'testEvictExpired'.

commit bfe4458448a59542713830f57713b3ac2af08e2b
Author: sboikov <sboikov@gridgain.com>
Date:   2016-09-28T11:31:24Z

    ignite-3621 Fixed 'testEvictExpired'.

commit bff34b50aa93d43c63f9419cf19e00c2d3cd5413
Author: Pavel Tupitsyn <ptupitsyn@apache.org>
Date:   2016-09-28T13:34:32Z

    IGNITE-3995 .NET: ASP.NET Session-State Store Provider run cache with default "null" name

commit 33b5efa0162941186318ae3d839ebdfcaecfdf27
Author: Pavel Tupitsyn <ptupitsyn@apache.org>
Date:   2016-09-28T13:52:09Z

    Fix the bug

commit be791f1480a11f6a17ba3b6ec7d17cdc9fd6352e
Author: Pavel Tupitsyn <ptupitsyn@apache.org>
Date:   2016-09-28T13:58:07Z


commit 486cb20ac30dcde82a13ae82de8fb2ed450e0eb0
Author: Pavel Tupitsyn <ptupitsyn@apache.org>
Date:   2016-09-28T13:59:04Z



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 infrastructure@apache.org or file a JIRA ticket
with INFRA.

View raw message