aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJunio C Hamano <gitster@pobox.com>2012-08-24 12:05:35 -0700
committerJunio C Hamano <gitster@pobox.com>2012-08-24 12:05:35 -0700
commit9dd8175be629c9ed5a102a42df1e6cc3f187eb64 (patch)
tree128eaa2a66e615cd6dce7e0dcda5f7330316c0f2
parent74b819aa31bbb436d46e03ab6ee1b82fb8da1b93 (diff)
parent03b05c7db5473329f433c5a3b87965d6fa0f691f (diff)
downloadgit-9dd8175be629c9ed5a102a42df1e6cc3f187eb64.tar.gz
git-9dd8175be629c9ed5a102a42df1e6cc3f187eb64.tar.xz
Merge branch 'hv/coding-guidelines' into maint-1.7.11
In earlier days, "imitate the style in the neibouring code" was sufficient to keep the coherent style, but over time some parts of the codebase have drifted enough to make it ineffective. * hv/coding-guidelines: Documentation/CodingGuidelines: spell out more shell guidelines
-rw-r--r--Documentation/CodingGuidelines8
1 files changed, 8 insertions, 0 deletions
diff --git a/Documentation/CodingGuidelines b/Documentation/CodingGuidelines
index 45577117c..57da6aade 100644
--- a/Documentation/CodingGuidelines
+++ b/Documentation/CodingGuidelines
@@ -76,11 +76,19 @@ For shell scripts specifically (not exhaustive):
- We do not use Process Substitution <(list) or >(list).
+ - Do not write control structures on a single line with semicolon.
+ "then" should be on the next line for if statements, and "do"
+ should be on the next line for "while" and "for".
+
- We prefer "test" over "[ ... ]".
- We do not write the noiseword "function" in front of shell
functions.
+ - We prefer a space between the function name and the parentheses. The
+ opening "{" should also be on the same line.
+ E.g.: my_function () {
+
- As to use of grep, stick to a subset of BRE (namely, no \{m,n\},
[::], [==], nor [..]) for portability.