{"thread":{"id":"35112","subject":"[PATCH] CodingGuidelines: style for multi-line comments","startedAt":"2013-10-12T00:45:46Z","lastAt":"2013-10-12T00:45:46Z","messageCount":1,"participants":["brian m. carlson"],"isPatch":true,"patchVersion":1,"patchTotal":null},"messages":[{"id":"228763","messageId":"1381538746-835885-1-git-send-email-sandals@crustytoothpaste.net","threadId":"35112","inReplyTo":null,"subject":"[PATCH] CodingGuidelines: style for multi-line comments","fromName":"brian m. carlson","fromEmail":"sandals@crustytoothpaste.net","sentAt":"2013-10-12T00:45:46Z","receivedAt":"2013-10-12T00:45:46Z","isPatch":true,"sender":{"key":"sandals@crustytoothpaste.net","avatar":"https://avatars.githubusercontent.com/u/497054?v=4"},"body":"The style for multi-line comments is often mentioned and should be documented\nfor clarity.\n\nSigned-off-by: brian m. carlson <sandals@crustytoothpaste.net>\n---\n Documentation/CodingGuidelines | 8 ++++++++\n 1 file changed, 8 insertions(+)\n\ndiff --git a/Documentation/CodingGuidelines b/Documentation/CodingGuidelines\nindex e5ca3b7..a584062 100644\n--- a/Documentation/CodingGuidelines\n+++ b/Documentation/CodingGuidelines\n@@ -145,6 +145,14 @@ For C programs:\n    they were describing changes.  Often splitting a function\n    into two makes the intention of the code much clearer.\n \n+ - Multi-line comments should include their delimiters on separate lines from\n+   the text. E.g.\n+\n+\t/*\n+\t * A very long\n+\t * multi-line comment.\n+\t */\n+\n  - Double negation is often harder to understand than no negation\n    at all.\n \n-- \n1.8.4\n"}]}