From ac51afb51c00693bb19c6a6110e9a45d2e4f79b7 Mon Sep 17 00:00:00 2001 From: Tom de Vries Date: Sat, 23 Nov 2024 12:20:34 +0100 Subject: [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 --- gdb/mi/mi-main.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'gdb/mi') diff --git a/gdb/mi/mi-main.c b/gdb/mi/mi-main.c index b72cd1b9..1d0fae9 100644 --- a/gdb/mi/mi-main.c +++ b/gdb/mi/mi-main.c @@ -2077,7 +2077,7 @@ mi_cmd_execute (struct mi_parse *parse) error (_("Invalid thread group for the --thread-group option")); set_current_inferior (inf); - /* This behaviour means that if --thread-group option identifies + /* This behavior means that if --thread-group option identifies an inferior with multiple threads, then a random one will be picked. This is not a problem -- frontend should always provide --thread if it wishes to operate on a specific -- cgit v1.1