From: Patrick Steinhardt Date: Wed, 24 Jul 2024 11:05:12 GMT Subject: [PATCH 1/3] Documentation: clarify indentation style for C preprocessor directives Message-ID: <64e0b449936a6828ead98438d621f7e7684546c8.1721818488.git.ps@pks.im> In-Reply-To: There has recently been some discussion around how C preprocessor directives shall be indented [1]. This discussion was settled towards indenting after the hash by two spaces [2]. Document it as such. [1]: https://lore.kernel.org/all/xmqqwmmm1bw6.fsf@gitster.g/ [2]: https://lore.kernel.org/all/20240708092317.267915-2-karthik.188@gmail.com/ Signed-off-by: Patrick Steinhardt --- Documentation/CodingGuidelines | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/Documentation/CodingGuidelines b/Documentation/CodingGuidelines index 1d92b2da03..1d09384f28 100644 --- a/Documentation/CodingGuidelines +++ b/Documentation/CodingGuidelines @@ -214,6 +214,16 @@ For C programs: - We use tabs to indent, and interpret tabs as taking up to 8 spaces. + - Nested C preprocessor directives are indented after the hash by two + spaces per nesting level. + + #if FOO + # include + # if BAR + # include + # endif + #endif + - We try to keep to at most 80 characters per line. - As a Git developer we assume you have a reasonably modern compiler -- 2.46.0.rc1.dirty