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

[PATCH v2] .clang-format: introduce the use of clang-format

From
Ramkumar Ramachandra <artagnon@gmail.com>
Date
Jan 21, 2015, 17:01 UTC
Message-ID
<1421859687-27216-1-git-send-email-artagnon@gmail.com>
In-Reply-To
<1421530221-39306-1-git-send-email-artagnon@gmail.com>

Instead of manually eyeballing style in reviews, just ask all contributors to run their patches through [git-]clang-format.

However, struct declarations that are combined with variable declaration and initialization get mangled:

        struct a {
                int n;
                const char *s;
        } arr[] = {
                { 1, "one" },
                { 2, "two" }
        };
becomes:
        struct a {
                int n;
                const char *s;
        } arr[] = { { 1, "one" }, { 2, "two" } };
It gets formatted better if arr is declared separately.
Helped-by: René Scharfe <l.s.r@web.de>
Signed-off-by: Ramkumar Ramachandra <artagnon@gmail.com>
---
 .clang-format | 11 +++++++++++
 1 file changed, 11 insertions(+)
 create mode 100644 .clang-format
diff --git a/.clang-format b/.clang-format
new file mode 100644
index 0000000..a336438
--- /dev/null
+++ b/.clang-format
@@ -0,0 +1,11 @@
+BasedOnStyle: LLVM
+IndentWidth: 8
+UseTab: Always
+BreakBeforeBraces: Linux
+AllowShortBlocksOnASingleLine: false
+AllowShortIfStatementsOnASingleLine: false
+IndentCaseLabels: false
+AllowShortFunctionsOnASingleLine: None
+ContinuationIndentWidth: 8
+Cpp11BracedListStyle: false
+BreakBeforeBraces: Stroustrup
-- 
2.2.1
Previous: Ramkumar RamachandraNext: Jeff King
Message 4 of 7 in “.clang-format: introduce the use of clang-format”
  1. .clang-format: introduce the use of clang-formatRamkumar Ramachandra, Jan 17, 2015
  2. René ScharfeJan 18, 2015
  3. Ramkumar RamachandraJan 21, 2015
  4. .clang-format: introduce the use of clang-formatRamkumar Ramachandra, Jan 21, 2015
  5. Jeff KingJan 21, 2015
  6. Ramkumar RamachandraJan 21, 2015
  7. Jeff KingJan 21, 2015

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.