diff options
author | Elijah Newren <newren@gmail.com> | 2019-11-05 17:07:20 +0000 |
---|---|---|
committer | Junio C Hamano <gitster@pobox.com> | 2019-11-07 13:42:00 +0900 |
commit | 031fd4b93b8182761948aa348565118955f48307 (patch) | |
tree | 2d4632eff752e87e9e417903584152f50d2d58ae /Documentation/CodingGuidelines | |
parent | 566a1439f6f56c2171b8853ddbca0ad3f5098770 (diff) | |
download | git-031fd4b93b8182761948aa348565118955f48307.tar.gz |
Documentation: fix a bunch of typos, both old and new
Reported-by: Jens Schleusener <Jens.Schleusener@fossies.org>
Signed-off-by: Elijah Newren <newren@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'Documentation/CodingGuidelines')
-rw-r--r-- | Documentation/CodingGuidelines | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/Documentation/CodingGuidelines b/Documentation/CodingGuidelines index f45db5b727..ed4e443a3c 100644 --- a/Documentation/CodingGuidelines +++ b/Documentation/CodingGuidelines @@ -75,7 +75,7 @@ For shell scripts specifically (not exhaustive): - If you want to find out if a command is available on the user's $PATH, you should use 'type <command>', instead of 'which <command>'. - The output of 'which' is not machine parseable and its exit code + The output of 'which' is not machine parsable and its exit code is not reliable across platforms. - We use POSIX compliant parameter substitutions and avoid bashisms; @@ -203,7 +203,7 @@ For C programs: . since early 2012 with e1327023ea, we have been using an enum definition whose last element is followed by a comma. This, like an array initializer that ends with a trailing comma, can be used - to reduce the patch noise when adding a new identifer at the end. + to reduce the patch noise when adding a new identifier at the end. . since mid 2017 with cbc0f81d, we have been using designated initializers for struct (e.g. "struct t v = { .val = 'a' };"). |