From: Nick Mathewson <nickm@torproject.org>
Date: Thu, 6 Apr 2017 12:53:26 +0000 (-0400)
Subject: Explain config_line_find() behavior on duplicates.
X-Git-Tag: tor-0.3.1.1-alpha~184^2
X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=5567a80caad0586b5d15db388339be4d276de136;p=thirdparty%2Ftor.git

Explain config_line_find() behavior on duplicates.
---

diff --git a/src/common/confline.c b/src/common/confline.c
index 6ec3b619dc..36f4c875f3 100644
--- a/src/common/confline.c
+++ b/src/common/confline.c
@@ -30,9 +30,11 @@ config_line_append(config_line_t **lst,
   (*lst) = newline;
 }
 
-/** Return the line in <b>lines</b> whose key is exactly <b>key</b>, or NULL
- * if no such key exists. For handling commandline-only options only; other
- * options should be looked up in the appropriate data structure. */
+/** Return the first line in <b>lines</b> whose key is exactly <b>key</b>, or
+ * NULL if no such key exists.
+ *
+ * (In options parsing, this is for handling commandline-only options only;
+ * other options should be looked up in the appropriate data structure.) */
 const config_line_t *
 config_line_find(const config_line_t *lines,
                  const char *key)