projects / tools / git-buildpackage.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: ba939cd) | patch
log: don't automatically setup gbp-specific logger
authorMarkus Lehtonen <markus.lehtonen@linux.intel.com>
Thu, 10 Jul 2014 06:42:35 +0000 (09:42 +0300)
committerJun Wang <junbill.wang@samsung.com>
Tue, 26 Jan 2016 19:54:41 +0000 (03:54 +0800)
commit6b8f8c3f09739118c7dd7706b011215645a5f2a1
tree47f013325c59151b3dbfdf4b7a7db59213a782d6tree | snapshot
parentba939cdf609837b6726a3e0869e456a463bbf0abcommit | diff
log: don't automatically setup gbp-specific logger

This makes it nicer to use gbp.* modules (e.g. gbp.git) in other
software projects which may have their own logging setup. After this
change, just importing gbp.* modules won't forcibly setup gbp-specific
logging. However, gbp logging is initialized whenever the
gbp.log.getLogger function is called which makes logging in existing gbp
commands behave just like before.

Signed-off-by: Markus Lehtonen <markus.lehtonen@linux.intel.com>
Domain: SCM / Build;