luo980/curl
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: remove him/her/he/she from documentation

Browse Source 
Closes #9208
This commit is contained in:
Marco Kamner 2022-07-27 13:52:53 +02:00 committed by Daniel Stenberg
parent 14f4e67ff6
commit 263409cf24
No known key found for this signature in database
GPG Key ID: 5CC908FDB71E12C2
3 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
docs/MAIL-ETIQUETTE
View File

@ -105,7 +105,7 @@ MAIL ETIQUETTE
messages" messages"
No matter what, we NEVER EVER respond to trolls or spammers on the list. If No matter what, we NEVER EVER respond to trolls or spammers on the list. If
you believe the list admin should do something in particular, contact him/her you believe the list admin should do something in particular, contact them
off-list. The subject will be taken care of as much as possible to prevent off-list. The subject will be taken care of as much as possible to prevent
repeated offenses, but responding on the list to such messages never leads to repeated offenses, but responding on the list to such messages never leads to
anything good and only puts the light even more on the offender: which was anything good and only puts the light even more on the offender: which was
@ -277,7 +277,7 @@ MAIL ETIQUETTE
one of the hints was what solved your problems. The guys who write answers one of the hints was what solved your problems. The guys who write answers
feel good to know that they provided a good answer and that you fixed the feel good to know that they provided a good answer and that you fixed the
problem. Far too often, the person who asked the question is never heard from problem. Far too often, the person who asked the question is never heard from
again, and we never get to know if he/she is gone because the problem was again, and we never get to know if they are gone because the problem was
solved or perhaps because the problem was unsolvable. solved or perhaps because the problem was unsolvable.
Getting the solution posted also helps other users that experience the same Getting the solution posted also helps other users that experience the same

2
docs/SECURITY-PROCESS.md
View File

@ -40,7 +40,7 @@ announcement.
- If the report is rejected, the team writes to the reporter to explain why. - If the report is rejected, the team writes to the reporter to explain why.
- If the report is accepted, the team writes to the reporter to let him/her - If the report is accepted, the team writes to the reporter to let them
know it is accepted and that they are working on a fix. know it is accepted and that they are working on a fix.
- The security team discusses the problem, works out a fix, considers the - The security team discusses the problem, works out a fix, considers the

2
src/tool_operate.c
View File

@ -1127,7 +1127,7 @@ static CURLcode single_transfer(struct GlobalConfig *global,
/* /*
* If the user has also selected --anyauth or --proxy-anyauth * If the user has also selected --anyauth or --proxy-anyauth
* we should warn him/her. * we should warn them.
*/ */
if(config->proxyanyauth || (authbits>1)) { if(config->proxyanyauth || (authbits>1)) {
warnf(global, warnf(global,