aboutsummaryrefslogtreecommitdiff
path: root/gdb/source-cache.c
diff options
context:
space:
mode:
authorTom de Vries <tdevries@suse.de>2024-10-08 08:24:13 +0200
committerTom de Vries <tdevries@suse.de>2024-10-08 08:24:13 +0200
commit0576fe8146527d871558d82d3e4e99d85f2115a7 (patch)
tree62f4cb2af514c69276e2da22ffb78ca34bade92a /gdb/source-cache.c
parent99fd53b19dddeb232e169cc5a3918a2adf7d3da2 (diff)
downloadgdb-0576fe8146527d871558d82d3e4e99d85f2115a7.zip
gdb-0576fe8146527d871558d82d3e4e99d85f2115a7.tar.gz
gdb-0576fe8146527d871558d82d3e4e99d85f2115a7.tar.bz2
[gdb/contrib] Add more separators in spellcheck.sh
Add two more separators in spellcheck.sh: colon and comma. Doing so triggers the "inbetween->between" rule, which gives an incorrect result. Override this with "inbetween->between, in between, in-between" [1], in a new file gdb/contrib/common-misspellings.txt. Fix the following common misspellings: ... everytime -> every time sucess -> success thru -> through transfered -> transferred inbetween -> between, in between, in-between ... Verified with spellcheck.sh. Tested on x86_64-linux. [1] https://www.grammarly.com/blog/commonly-confused-words/in-between-or-inbetween/
Diffstat (limited to 'gdb/source-cache.c')
0 files changed, 0 insertions, 0 deletions