You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@ignite.apache.org by akuramshingg <gi...@git.apache.org> on 2017/05/25 11:24:05 UTC

[GitHub] ignite pull request #2005: ignite-4496-1

GitHub user akuramshingg opened a pull request:

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

    ignite-4496-1

    IGNITE-4496 Review all logging for sensitive data leak

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

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

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

    https://github.com/apache/ignite/pull/2005.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 #2005
    
----
commit db02d5a0abb3b27d26f19b37daac0ad7d4cd7744
Author: Alexandr Kuramshin <ei...@gmail.com>
Date:   2017-05-25T11:05:40Z

    IGNITE-4496 Review all logging for sensitive data leak

commit 281d5e8227fc360198d574211f6224db5d48a59d
Author: Alexandr Kuramshin <ei...@gmail.com>
Date:   2017-05-25T11:22:27Z

    log.debug() fix
    remove empty files

----


---
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.
---