[slf4j-dev] [GIT] SLF4J: Simple Logging Facade for Java branch, master, updated. v_1.6.1-34-gd9e7175
added by portage for gitosis-gentoo
git-noreply at pixie.qos.ch
Thu Jun 16 11:29:55 CEST 2011
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 d9e7175fb77832e2366a5755995bb14399f015fa (commit)
via d380a0953e126827e9efbbb501a7352b17bb21f2 (commit)
from ebf05781718598adebd1e8fc058f459891002682 (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=d9e7175fb77832e2366a5755995bb14399f015fa
http://github.com/ceki/slf4j/commit/d9e7175fb77832e2366a5755995bb14399f015fa
commit d9e7175fb77832e2366a5755995bb14399f015fa
Merge: d380a09 ebf0578
Author: Ceki Gulcu <ceki at qos.ch>
Date: Thu Jun 16 11:22:26 2011 +0200
Merge branch 'master' of git.qos.ch:slf4j
http://git.qos.ch/gitweb/?p=slf4j.git;a=commit;h=d380a0953e126827e9efbbb501a7352b17bb21f2
http://github.com/ceki/slf4j/commit/d380a0953e126827e9efbbb501a7352b17bb21f2
commit d380a0953e126827e9efbbb501a7352b17bb21f2
Author: Ceki Gulcu <ceki at qos.ch>
Date: Thu Jun 16 11:22:09 2011 +0200
precision regarding logback
diff --git a/slf4j-site/src/site/pages/faq.html b/slf4j-site/src/site/pages/faq.html
index 155f4df..ecd5d48 100644
--- a/slf4j-site/src/site/pages/faq.html
+++ b/slf4j-site/src/site/pages/faq.html
@@ -194,12 +194,13 @@
<dd>
<p>In short, libraries and other embedded components should
- consider SLF4J for their logging needs because libraries
- cannot afford to impose their choice of logging system on the
- end-user. On the other hand, it does not necessarily make
- sense for stand-alone applications to use SLF4J. Stand-alone
- applications can invoke the logging system of their choice
- directly.
+ consider SLF4J for their logging needs because libraries cannot
+ afford to impose their choice of logging framework on the
+ end-user. On the other hand, it does not necessarily make sense
+ for stand-alone applications to use SLF4J. Stand-alone
+ applications can invoke the logging framework of their choice
+ directly. In the case of logback, the question is moot because
+ logback exposes its logger API via SLF4J.
</p>
<p>SLF4J is only a facade, meaning that it does not provide a
-----------------------------------------------------------------------
Summary of changes:
slf4j-site/src/site/pages/faq.html | 13 +++++++------
1 files changed, 7 insertions(+), 6 deletions(-)
hooks/post-receive
--
SLF4J: Simple Logging Facade for Java
More information about the slf4j-dev
mailing list