projects / horde.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 49a029c) | patch
Only show backtrace if logging at DEBUG level
authorMichael M Slusarz <slusarz@curecanti.org>
Mon, 24 Jan 2011 23:51:55 +0000 (16:51 -0700)
committerMichael M Slusarz <slusarz@curecanti.org>
Tue, 25 Jan 2011 00:04:56 +0000 (17:04 -0700)
commitd81fb920cea084aa176e6f0518fdf6dbd035d57d
tree750625171f56684fb8d9b84fb1455ce7e1cd8a41tree | snapshot
parent49a029c817c3c855fc9a92fff406bc65bcd06711commit | diff
Only show backtrace if logging at DEBUG level

Otherwise, things like framework libraries that throw exceptions and
provide way of logging exceptions (e.g. Horde_Imap_Client) give
backtraces for items that should not need to be logged (e.g.
authentication failures).
framework/Core/lib/Horde/Core/Log/Logger.php diff | blob | history
Unnamed repository; edit this file to name it for gitweb.