summaryrefslogtreecommitdiff
path: root/Documentation/CodingGuidelines
diff options
context:
space:
mode:
authorLibravatar Junio C Hamano <gitster@pobox.com>2014-04-09 12:03:26 -0700
committerLibravatar Junio C Hamano <gitster@pobox.com>2014-04-09 12:03:26 -0700
commit3c9e56b75c4a9a6832d94a00f079ea68e8a281ca (patch)
tree5f5b11703f64319bcb71603c825d382f4703a763 /Documentation/CodingGuidelines
parentMerge branch 'cn/fetch-prune-overlapping-destination' into maint (diff)
parentcode and test: fix misuses of "nor" (diff)
downloadtgif-3c9e56b75c4a9a6832d94a00f079ea68e8a281ca.tar.xz
Merge branch 'jl/nor-or-nand-and' into maint
* jl/nor-or-nand-and: code and test: fix misuses of "nor" comments: fix misuses of "nor" contrib: fix misuses of "nor" Documentation: fix misuses of "nor"
Diffstat (limited to 'Documentation/CodingGuidelines')
-rw-r--r--Documentation/CodingGuidelines4
1 files changed, 2 insertions, 2 deletions
diff --git a/Documentation/CodingGuidelines b/Documentation/CodingGuidelines
index ef67b53f72..b99fa87f68 100644
--- a/Documentation/CodingGuidelines
+++ b/Documentation/CodingGuidelines
@@ -91,13 +91,13 @@ For shell scripts specifically (not exhaustive):
E.g.: my_function () {
- As to use of grep, stick to a subset of BRE (namely, no \{m,n\},
- [::], [==], nor [..]) for portability.
+ [::], [==], or [..]) for portability.
- We do not use \{m,n\};
- We do not use -E;
- - We do not use ? nor + (which are \{0,1\} and \{1,\}
+ - We do not use ? or + (which are \{0,1\} and \{1,\}
respectively in BRE) but that goes without saying as these
are ERE elements not BRE (note that \? and \+ are not even part
of BRE -- making them accessible from BRE is a GNU extension).