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

Posted to notifications@logging.apache.org by mikebski <gi...@git.apache.org> on 2018/05/02 14:21:35 UTC

[GitHub] logging-log4j2 pull request #172: Fix for https://issues.apache.org/jira/bro...

GitHub user mikebski opened a pull request:

    https://github.com/apache/logging-log4j2/pull/172

    Fix for https://issues.apache.org/jira/browse/LOG4J2-2331

    Fix for https://issues.apache.org/jira/browse/LOG4J2-2331 - use logger string formatting instead of concatenation

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

    $ git pull https://github.com/mikebski/logging-log4j2 master

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

    https://github.com/apache/logging-log4j2/pull/172.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 #172
    
----
commit 534cf03241314a67a6a9bc11b45e923b0bb76d43
Author: Mike Baranski <ba...@...>
Date:   2018-05-02T14:20:30Z

    Fix for https://issues.apache.org/jira/browse/LOG4J2-2331 - use logger string formatting instead of concatenation

----


---

[GitHub] logging-log4j2 pull request #172: Fix for https://issues.apache.org/jira/bro...

Posted by asfgit <gi...@git.apache.org>.

Github user asfgit closed the pull request at:

    https://github.com/apache/logging-log4j2/pull/172


---

[GitHub] logging-log4j2 issue #172: Fix for https://issues.apache.org/jira/browse/LOG...

Posted by rgoers <gi...@git.apache.org>.

Github user rgoers commented on the issue:

    https://github.com/apache/logging-log4j2/pull/172
  
    This PR was merged in May but apparently neglected to use the format to trigger github to close it.


---