diff options
| author |  Junio C Hamano <gitster@pobox.com> | 2012-08-24 12:05:35 -0700 |
|---|---|---|
| committer | Junio C Hamano <gitster@pobox.com> | 2012-08-24 12:05:35 -0700 |
| commit | 9dd8175be629c9ed5a102a42df1e6cc3f187eb64 (patch) | |
| tree | 128eaa2a66e615cd6dce7e0dcda5f7330316c0f2 /Documentation | |
| parent | Merge branch 'jc/tag-doc' into maint-1.7.11 (diff) | |
| parent | Documentation/CodingGuidelines: spell out more shell guidelines (diff) | |
| download | tgif-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
Diffstat (limited to 'Documentation')
| -rw-r--r-- | Documentation/CodingGuidelines | 8 |
1 files changed, 8 insertions, 0 deletions
diff --git a/Documentation/CodingGuidelines b/Documentation/CodingGuidelines index 45577117c2..57da6aadeb 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. |