summaryrefslogtreecommitdiff
path: root/Documentation/CodingGuidelines
diff options
context:
space:
mode:
authorGiuseppe Bilotta <giuseppe.bilotta@gmail.com>2010-12-03 17:47:35 +0100
committerJunio C Hamano <gitster@pobox.com>2010-12-03 15:22:59 -0800
commitf36a4fa8ef611c37c890ed21a388a5ece801a3de (patch)
tree189263321a9d98008fdebb8541b9b5e0cf55bd5f /Documentation/CodingGuidelines
parent3bae8d4da1ee7fce0cf1ef9fcf49656ca1e48769 (diff)
downloadgit-f36a4fa8ef611c37c890ed21a388a5ece801a3de.tar.gz
CodingGuidelines: mention whitespace preferences for shell scripts
Signed-off-by: Giuseppe Bilotta <giuseppe.bilotta@gmail.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'Documentation/CodingGuidelines')
-rw-r--r--Documentation/CodingGuidelines4
1 files changed, 4 insertions, 0 deletions
diff --git a/Documentation/CodingGuidelines b/Documentation/CodingGuidelines
index 09ffc46563..46f8a3fab1 100644
--- a/Documentation/CodingGuidelines
+++ b/Documentation/CodingGuidelines
@@ -31,6 +31,10 @@ But if you must have a list of rules, here they are.
For shell scripts specifically (not exhaustive):
+ - We use tabs for indentation.
+
+ - Case arms are indented at the same depth as case and esac lines.
+
- We prefer $( ... ) for command substitution; unlike ``, it
properly nests. It should have been the way Bourne spelled
it from day one, but unfortunately isn't.