This is an automated email from the ASF dual-hosted git repository.

bdelacretaz pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/sling-site.git


The following commit(s) were added to refs/heads/master by this push:
     new 41e8304  Fix logging tag and title
41e8304 is described below

commit 41e8304e2557cc07b1e8fa2b66f7483cff932fd2
Author: Bertrand Delacretaz <bdelacre...@apache.org>
AuthorDate: Wed Apr 11 09:52:15 2018 +0200

    Fix logging tag and title
---
 .../jbake/content/documentation/development/client-request-logging.md   | 2 +-
 src/main/jbake/content/documentation/legacy/logging.md                  | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git 
a/src/main/jbake/content/documentation/development/client-request-logging.md 
b/src/main/jbake/content/documentation/development/client-request-logging.md
index b58d32e..9a9f2ec 100644
--- a/src/main/jbake/content/documentation/development/client-request-logging.md
+++ b/src/main/jbake/content/documentation/development/client-request-logging.md
@@ -1,7 +1,7 @@
 title=Client Request Logging           
 type=page
 status=published
-tags=requests,operations
+tags=requests,operations,logging
 ~~~~~~
 
 Sling provides extensive support to log various information at the before and 
after processing client requests. Out of the box, there are two loggers 
configured to write traditional `access.log` and `request.log` files. In 
addition more logging can be configured by providing OSGi Configuration Admin 
configuration.
diff --git a/src/main/jbake/content/documentation/legacy/logging.md 
b/src/main/jbake/content/documentation/legacy/logging.md
index 3128daa..5c0ce84 100644
--- a/src/main/jbake/content/documentation/legacy/logging.md
+++ b/src/main/jbake/content/documentation/legacy/logging.md
@@ -1,4 +1,4 @@
-title=Logging          
+title=Logging (Legacy 3.x)
 type=page
 status=published
 tags=logging,operations

-- 
To stop receiving notification emails like this one, please contact
bdelacre...@apache.org.

Reply via email to