From 665e30f74d8cd237a5a9923157380d60e1ffb4e5 Mon Sep 17 00:00:00 2001 From: Benjamin Kaduk Date: Sun, 14 Jan 2024 15:45:55 -0800 Subject: [PATCH] CODING: discuss indentation for non-C files Right now, that's just Makefile and plain text. We'll want to add more eventually. Change-Id: I10c559fe94c7c634e1de6d98020a1c7a391da2b4 Reviewed-on: https://gerrit.openafs.org/15629 Reviewed-by: Michael Meffie Reviewed-by: Mark Vitale Reviewed-by: Cheyenne Wills Reviewed-by: Benjamin Kaduk Tested-by: Benjamin Kaduk --- CODING | 12 ++++++++++-- 1 file changed, 10 insertions(+), 2 deletions(-) diff --git a/CODING b/CODING index d6db6e6aab..98e1e33a2c 100644 --- a/CODING +++ b/CODING @@ -9,8 +9,9 @@ review to cover, and discusses how we handle compiler warnings. Prototyping and Style ===================== -We have an official style. Please use it. If you have gnu indent 2.2.9 or -later you can format new files for this style with the following options: +We have an official style for C code. Please use it. If you have gnu indent +2.2.9 or later you can format new files for this style with the following +options: -npro -nbad -bap -nbc -bbo -br -ce -cdw -brs -ncdb -cp1 -ncs -di2 -ndj -nfc1 -nfca -i4 -lp -npcs -nprs -psl -sc -nsob -ts8 @@ -21,6 +22,13 @@ initial style cleanup commit before making sweeping changes to a given file, and otherwise try to accommodate the prevailing style in the file when making minor changes. +The style for non-C code varies. Makefiles must use literal tabs to +indent rule bodies, but use spaces for any additional indentation +needed. Plain text files (such as this one) should use spaces for +indentation, with a 4-space indent as the default when one is needed. +Other cases will be added here as they are encountered and a consensus +determined for how to handle them. + Prototypes for all source files in a given dir DDD should be placed in the file DDD/DDD_prototypes.h. All externally used (either API or used by other source files) routines and variables should be