git/list[1] front-page[2] threads[3] people[4] search[5] about
 

[PATCH] doc: reword gitworflows for neutrality

From
Daniel Bensoussan <daniel.bensoussan--bohm@etu.univ-lyon1.fr>
Date
Dec 8, 2017, 15:18 UTC
Message-ID
<20171208151807.3569-1-daniel.bensoussan--bohm@etu.univ-lyon1.fr>
Changed 'he' to 'them' to be more neutral in "gitworkflows.txt".
See discussion at: https://public-inbox.org/git/xmqqvahieeqy.fsf@gitster.mtv.corp.google.com/
Signed-off-by: Matthieu Moy <matthieu.moy@univ-lyon1.fr>
Signed-off-by: Timothee Albertin <timothee.albertin@etu.univ-lyon1.fr>
Signed-off-by: Nathan Payre <nathan.payre@etu.univ-lyon1.fr>
Signed-off-by: Daniel Bensoussan <daniel.bensoussan--bohm@etu.univ-lyon1.fr>
---
 Documentation/gitworkflows.txt | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/Documentation/gitworkflows.txt b/Documentation/gitworkflows.txt
index 02569d0..926e044 100644
--- a/Documentation/gitworkflows.txt
+++ b/Documentation/gitworkflows.txt
@@ -407,8 +407,8 @@ follows.
 `git pull <url> <branch>`
 =====================================
 
-Occasionally, the maintainer may get merge conflicts when he tries to
-pull changes from downstream.  In this case, he can ask downstream to
+Occasionally, the maintainer may get merge conflicts when they try to
+pull changes from downstream.  In this case, they can ask downstream to
 do the merge and resolve the conflicts themselves (perhaps they will
 know better how to resolve them).  It is one of the rare cases where
 downstream 'should' merge from upstream.
-- 
2.11.0
Next: Eric Sunshine
Message 1 of 3 in “doc: reword gitworflows for neutrality”
  1. doc: reword gitworflows for neutralityDaniel Bensoussan, Dec 8, 2017
  2. Eric SunshineDec 8, 2017
  3. BENSOUSSAN--BOHM DANIEL p1507430Dec 10, 2017

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.