summaryrefslogtreecommitdiff
path: root/Documentation/CodingGuidelines
diff options
context:
space:
mode:
authorJunio C Hamano <gitster@pobox.com>2014-04-30 21:25:47 (GMT)
committerJunio C Hamano <gitster@pobox.com>2014-05-02 20:26:07 (GMT)
commit691d0dd0a9c901286c2a0a28c30ec4d13bcd2032 (patch)
treea266bd4edc39786ff42854a5118d5e27f1f43cf9 /Documentation/CodingGuidelines
parent6117a3d4946e35c7d4a38c0b443891c81808a838 (diff)
downloadgit-691d0dd0a9c901286c2a0a28c30ec4d13bcd2032.zip
git-691d0dd0a9c901286c2a0a28c30ec4d13bcd2032.tar.gz
git-691d0dd0a9c901286c2a0a28c30ec4d13bcd2032.tar.bz2
CodingGuidelines: do not call the conditional statement "if()"
The point immediately before it is about having SP after the control keyword. Spell it out as 'an "if" statement' instead. Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'Documentation/CodingGuidelines')
-rw-r--r--Documentation/CodingGuidelines2
1 files changed, 1 insertions, 1 deletions
diff --git a/Documentation/CodingGuidelines b/Documentation/CodingGuidelines
index 0a574b2..aeaa824 100644
--- a/Documentation/CodingGuidelines
+++ b/Documentation/CodingGuidelines
@@ -194,7 +194,7 @@ For C programs:
of "else if" statements, it can make sense to add braces to
single line blocks.
- - We try to avoid assignments inside if().
+ - We try to avoid assignments in the condition of an "if" statement.
- Try to make your code understandable. You may put comments
in, but comments invariably tend to stale out when the code