diff options
| author | Peter Powell <petpow@saberuk.com> | 2019-06-07 19:47:15 +0100 |
|---|---|---|
| committer | Peter Powell <petpow@saberuk.com> | 2019-06-07 20:22:43 +0100 |
| commit | f6b33a8facd6ca200292786c1061782c41cdd278 (patch) | |
| tree | 429c0063f9174e3bf0a5134aa5eb8737287ca934 /src/modules/extra | |
| parent | 638e4bb417ebcd4f0a384ac19585620b0fde1569 (diff) | |
Replace all abstract usages of his/he/her with they/their/it.
Diffstat (limited to 'src/modules/extra')
| -rw-r--r-- | src/modules/extra/m_mysql.cpp | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/src/modules/extra/m_mysql.cpp b/src/modules/extra/m_mysql.cpp index 4f727519f..6a9f38b6c 100644 --- a/src/modules/extra/m_mysql.cpp +++ b/src/modules/extra/m_mysql.cpp @@ -68,7 +68,7 @@ * The ircd thread then mutexes the queue once more, reads the outbound response off the head * of the queue, and sends it on its way to the original calling module. * - * XXX: You might be asking "why doesnt he just send the response from within the worker thread?" + * XXX: You might be asking "why doesnt it just send the response from within the worker thread?" * The answer to this is simple. The majority of InspIRCd, and in fact most ircd's are not * threadsafe. This module is designed to be threadsafe and is careful with its use of threads, * however, if we were to call a module's OnRequest even from within a thread which was not the |