CLEANUP: log: remove ambiguous legacy comment for resolve_logger()

It is no longer relevant to say that <logger> is used for implicit
settings. In fact the function resolves <logger>, but currently
mainly focuses on loggers's target. However we could extend the
function to perform additional work on the logger itself in the future.

let's adjust the comment to prevent any confusion.

diff --git a/src/log.c b/src/log.c
index 0cd704da9f6df748a000de460f9cd4c82080a0f5..862e0299db37382b1209a23d0ccc5f3bcaeaae1a 100644 (file)
--- a/src/log.c
+++ b/src/log.c
@@ -1406,8 +1406,6 @@ static int postcheck_log_backend(struct proxy *be)
 /* resolves a single logger entry (it is expected to be called
  * at postparsing stage)
  *
- * <logger> is parent logger used for implicit settings
- *
  * Returns err_code which defaults to ERR_NONE and can be set to a combination
  * of ERR_WARN, ERR_ALERT, ERR_FATAL and ERR_ABORT in case of errors.
  * <msg> could be set at any time (it will usually be set on error, but