[slf4j-dev] [GIT] SLF4J: Simple Logging Facade for Java branch, master, updated. v_1.6.1-9-gdb5d1d0

[added by portage for gitosis-gentoo]

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "SLF4J: Simple Logging Facade for Java".

The branch, master has been updated
       via  db5d1d0834c0f1eb4d7b0612efb2e2928e337dca (commit)
      from  36d3a0d6d081424bf40ddf10b7e5479a14a216ef (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
http://git.qos.ch/gitweb/?p=slf4j.git;a=commit;h=db5d1d0834c0f1eb4d7b0612efb2e2928e337dca
http://github.com/ceki/slf4j/commit/db5d1d0834c0f1eb4d7b0612efb2e2928e337dca

commit db5d1d0834c0f1eb4d7b0612efb2e2928e337dca
Author: Ceki Gulcu <ceki at qos.ch>
Date:   Fri Oct 8 18:39:56 2010 +0200

    minor edits

diff --git a/slf4j-site/src/site/pages/faq.html b/slf4j-site/src/site/pages/faq.html
index d079147..79c026c 100644
--- a/slf4j-site/src/site/pages/faq.html
+++ b/slf4j-site/src/site/pages/faq.html
@@ -541,11 +541,13 @@ org.slf4j.impl.StaticLoggerBinder.SINGLETON from class org.slf4j.LoggerFactory
       along, code that uses the wrapper will be equally difficult to
       migrate to the new API as code that used SLF4J directly. Thus,
       the wrapper is not likely to future-proof your code, but to make
-      it heavier by adding an additional indirection on top SLF4J
-      which is an indirection in itself. It's actually a lot worse
-      than that. Wrappers will need to depend on certain internal
-      SLF4J interfaces which change from time to time, typical on each
-      major series, contrary to the client-facing API which never
+      it more complex by adding an additional indirection on top of
+      SLF4J, which is an indirection in itself. 
+      </p>
+
+      <p>It is actually worse than that. Wrappers will need to depend
+      on certain internal SLF4J interfaces which change from time to
+      time, contrary to the client-facing API which never
       changes. Thus, wrappers are usually dependent on the major
       version they were compiled with. A wrapper compiled against
       SLF4J version 1.5.x will not work with SLF4J 1.6 whereas client

-----------------------------------------------------------------------

Summary of changes:
 slf4j-site/src/site/pages/faq.html |   12 +++++++-----
 1 files changed, 7 insertions(+), 5 deletions(-)


hooks/post-receive
-- 
SLF4J: Simple Logging Facade for Java