From ac51afb51c00693bb19c6a6110e9a45d2e4f79b7 Mon Sep 17 00:00:00 2001
From: Tom de Vries <tdevries@suse.de>
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/python/py-connection.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
(limited to 'gdb/python/py-connection.c')
diff --git a/gdb/python/py-connection.c b/gdb/python/py-connection.c
index 1fdcd73..7b5146d 100644
--- a/gdb/python/py-connection.c
+++ b/gdb/python/py-connection.c
@@ -342,7 +342,7 @@ struct py_send_packet_callbacks : public send_remote_packet_callbacks
It is important that the result is inspected immediately after sending
a packet to the remote, and any error fetched, calling any other
Python functions that might clear the error state, or rely on an error
- not being set will cause undefined behaviour. */
+ not being set will cause undefined behavior. */
gdbpy_ref<> result () const
{
--
cgit v1.1