aboutsummaryrefslogtreecommitdiff
path: root/gdb/contrib
diff options
context:
space:
mode:
authorTom de Vries <tdevries@suse.de>2024-11-23 12:20:34 +0100
committerTom de Vries <tdevries@suse.de>2024-11-23 12:20:34 +0100
commitac51afb51c00693bb19c6a6110e9a45d2e4f79b7 (patch)
treeb2fcf9ded59d04633dbb406083e2814c34e4e468 /gdb/contrib
parent63eedf3b09f73077ecff2118f45d1adb1391eddd (diff)
downloadbinutils-ac51afb51c00693bb19c6a6110e9a45d2e4f79b7.zip
binutils-ac51afb51c00693bb19c6a6110e9a45d2e4f79b7.tar.gz
binutils-ac51afb51c00693bb19c6a6110e9a45d2e4f79b7.tar.bz2
[gdb/contrib] Add two rules in common-misspellings.txt
Eli mentioned [1] that given that we use US English spelling in our documentation, we should use "behavior" instead of "behaviour". In wikipedia-common-misspellings.txt there's a rule: ... behavour->behavior, behaviour ... which leaves this as a choice. Add an overriding rule to hardcode the choice to common-misspellings.txt: ... behavour->behavior ... and add a rule to rewrite behaviour into behavior: ... behaviour->behavior ... and re-run spellcheck.sh on gdb*. Tested on x86_64-linux. [1] https://sourceware.org/pipermail/gdb-patches/2024-November/213371.html
Diffstat (limited to 'gdb/contrib')
-rw-r--r--gdb/contrib/common-misspellings.txt2
-rwxr-xr-xgdb/contrib/gdb-add-index.sh2
2 files changed, 3 insertions, 1 deletions
diff --git a/gdb/contrib/common-misspellings.txt b/gdb/contrib/common-misspellings.txt
index 11ca8ec..4ab968e 100644
--- a/gdb/contrib/common-misspellings.txt
+++ b/gdb/contrib/common-misspellings.txt
@@ -20,6 +20,8 @@
inbetween->between, in between, in-between
sofar->so far
doens't->doesn't
+behavour->behavior
+behaviour->behavior
# Identity rules.
diff --git a/gdb/contrib/gdb-add-index.sh b/gdb/contrib/gdb-add-index.sh
index bd5a8f7..00a9bea 100755
--- a/gdb/contrib/gdb-add-index.sh
+++ b/gdb/contrib/gdb-add-index.sh
@@ -122,7 +122,7 @@ $GDB --batch -nx -iex 'set auto-load no' \
# In some situations gdb can exit without creating an index. This is
# not an error.
-# E.g., if $file is stripped. This behaviour is akin to stripping an
+# E.g., if $file is stripped. This behavior is akin to stripping an
# already stripped binary, it's a no-op.
status=0