path: root/Documentation/git-push.txt
diff options
authorFelipe Contreras <>2021-06-15 14:11:09 (GMT)
committerJunio C Hamano <>2021-06-16 02:25:09 (GMT)
commit69b3367f6c987b36b98937d8f446f75c5dbc000a (patch)
tree0e09e9f4c16702e4a839d6c9bc5ad8ef0e487de3 /Documentation/git-push.txt
parent48bf2fa8bad054d66bd79c6ba903c89c704201f7 (diff)
doc: avoid using the gender of other people
Using gendered pronouns for an anonymous person applies a gender where none is known and further excludes readers who do not use gendered pronouns. Avoid such examples in the documentation by using "they" or passive voice to avoid the need for a pronoun. Inspired-by: Derrick Stolee <> Signed-off-by: Felipe Contreras <> Signed-off-by: Derrick Stolee <> Signed-off-by: Junio C Hamano <>
Diffstat (limited to 'Documentation/git-push.txt')
1 files changed, 2 insertions, 2 deletions
diff --git a/Documentation/git-push.txt b/Documentation/git-push.txt
index ab103c8..48cf37b 100644
--- a/Documentation/git-push.txt
+++ b/Documentation/git-push.txt
@@ -244,8 +244,8 @@ Imagine that you have to rebase what you have already published.
You will have to bypass the "must fast-forward" rule in order to
replace the history you originally published with the rebased history.
If somebody else built on top of your original history while you are
-rebasing, the tip of the branch at the remote may advance with her
-commit, and blindly pushing with `--force` will lose her work.
+rebasing, the tip of the branch at the remote may advance with their
+commit, and blindly pushing with `--force` will lose their work.
This option allows you to say that you expect the history you are
updating is what you rebased and want to replace. If the remote ref