[GitHub] geode pull request #482: gfsh help now uses log4j log levels: update user gu...

[davebarnes97]

Github user davebarnes97 closed the pull request at:

https://github.com/apache/geode/pull/482


---
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] geode pull request #482: gfsh help now uses log4j log levels: update user gu...

[davebarnes97]

GitHub user davebarnes97 opened a pull request:

https://github.com/apache/geode/pull/482

gfsh help now uses log4j log levels: update user guide

Where gfsh documentation listed log level params, replaced the "old" levels 
(fine, finer, finest, etc) with log4j levels (ALL, TRACE, DEBUG, etc).
Did not replace log level params in non-gfsh contexts (e.g. Java command 
lines or xml config files).
Also did not standardize "loglevel" vs "log-level", which are 
inconsistently used in the gfsh interface (see GEODE-2850).

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

$ git pull https://github.com/davebarnes97/geode feature/GEODE-2778

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

https://github.com/apache/geode/pull/482.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 #482


commit 29177fed58851868c698f9c24c7424903ea22461
Author: Dave Barnes 
Date:   2017-04-28T22:55:50Z

gfsh help now uses log4j log levels: update user guide




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