git/list[1] front-page[2] threads[3] people[4] search[5] about
 

[PATCH] CodingGuidelines: style for multi-line comments

From
brian m. carlson <sandals@crustytoothpaste.net>
Date
Oct 12, 2013, 00:45 UTC
Message-ID
<1381538746-835885-1-git-send-email-sandals@crustytoothpaste.net>

The style for multi-line comments is often mentioned and should be documented for clarity.

Signed-off-by: brian m. carlson <sandals@crustytoothpaste.net>
---
 Documentation/CodingGuidelines | 8 ++++++++
 1 file changed, 8 insertions(+)
diff --git a/Documentation/CodingGuidelines b/Documentation/CodingGuidelines
index e5ca3b7..a584062 100644
--- a/Documentation/CodingGuidelines
+++ b/Documentation/CodingGuidelines
@@ -145,6 +145,14 @@ For C programs:
    they were describing changes.  Often splitting a function
    into two makes the intention of the code much clearer.
 
+ - Multi-line comments should include their delimiters on separate lines from
+   the text. E.g.
+
+	/*
+	 * A very long
+	 * multi-line comment.
+	 */
+
  - Double negation is often harder to understand than no negation
    at all.
 
-- 
1.8.4
Message 1 of 1 in “CodingGuidelines: style for multi-line comments”
  1. CodingGuidelines: style for multi-line commentsbrian m. carlson, Oct 12, 2013

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.