Google Git
Sign in
android / platform / external / slf4j / refs/heads/pie-qpr2-release
commit22558c51ff8a9a9d8314a13febb665083bb5986a[log] [tgz]
authorJiyong Park <[email protected]>Mon Feb 19 06:25:58 2018 +0000
committerandroid-build-merger <[email protected]>Mon Feb 19 06:25:58 2018 +0000
tree499fd6f497a792c4d9079324405e65817cf0161b
parent63b140791fbb0bceabc496bdd29e108d9597b044 [diff]
parent0343c9ac444e0ab3b6abc7262da4afcf88b801c1 [diff]
Build with core_current am: 8ed83fa0a4 am: 47fb8554d4
am: 0343c9ac44

Change-Id: I6aa601e524cbf6f4203a0a5b47a8f01a109fa0d2
tree: 499fd6f497a792c4d9079324405e65817cf0161b
  1. .idea/
  2. integration/
  3. jcl-over-slf4j/
  4. jul-to-slf4j/
  5. log4j-over-slf4j/
  6. osgi-over-slf4j/
  7. slf4j-android/
  8. slf4j-api/
  9. slf4j-ext/
  10. slf4j-jcl/
  11. slf4j-jdk14/
  12. slf4j-log4j12/
  13. slf4j-migrator/
  14. slf4j-nop/
  15. slf4j-simple/
  16. slf4j-site/
  17. src/
  18. .gitattributes
  19. .gitignore
  20. .travis.yml
  21. Android.mk
  22. binderVersion.pl
  23. codeStyle.xml
  24. goVersion.sh
  25. LICENSE.txt
  26. MODULE_LICENSE_MIT
  27. NOTICE
  28. pom.xml
  29. README.md
  30. test
  31. version.pl
README.md

About SLF4J

The Simple Logging Facade for Java (SLF4J) serves as a simple facade or abstraction for various logging frameworks (e.g. java.util.logging, logback, log4j) allowing the end user to plug in the desired logging framework at deployment time. More information can be found on the SLF4J website.

Build Status

Build Status

How to contribute pull requests

If you are interested in improving SLF4J, great! The SLF4J community looks forward to your contribution. Please follow this process:

  1. Start a discussion on the slf4j-dev mailing list about your proposed change. Alternately file a bug report.
  2. Fork qos-ch/slf4j. Ideally, create a new branch from your fork for your contribution to make it easier to merge your changes back.
  3. Make your changes on the branch you hopefuly created in Step 2. Be sure that your code passes existing unit tests. Please add unit tests for your work if appropriate. It usually is.
  4. Push your changes to your fork/branch in github. Don't push it to your master! If you do it will make it harder to submit new changes later.
  5. Submit a pull request to SLF4J from from your commit page on github.