From 9b718ec7f49533df0e650411aba5bba73ad08289 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?G=C3=A1bor=20Hojtsy?= <gabor@hojtsy.hu>
Date: Fri, 6 Aug 2010 11:08:11 +0000
Subject: [PATCH] #782442 by nenne, rdrh555: better documentation on what can
be a watchdog message type
---
includes/bootstrap.inc | 6 ++++--
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/includes/bootstrap.inc b/includes/bootstrap.inc
index e170f27ac12f..3b3f8334277e 100644
--- a/includes/bootstrap.inc
+++ b/includes/bootstrap.inc
@@ -914,7 +914,8 @@ function request_uri() {
* Log a system message.
*
* @param $type
- * The category to which this message belongs.
+ * The category to which this message belongs. Can be any string, but the
+ * general practice is to use the name of the module calling watchdog().
* @param $message
* The message to store in the log. See t() for documentation
* on how $message and $variables interact. Keep $message
@@ -924,7 +925,8 @@ function request_uri() {
* NULL if message is already translated or not possible to
* translate.
* @param $severity
- * The severity of the message, as per RFC 3164
+ * The severity of the message, as per RFC 3164. Possible values are
+ * WATCHDOG_ERROR, WATCHDOG_WARNING, etc.
* @param $link
* A link to associate with the message.
*
--
GitLab