summaryrefslogtreecommitdiff
path: root/HACKING
diff options
context:
space:
mode:
authorChristophe Fergeau <cfergeau@redhat.com>2014-12-08 14:13:00 +0100
committerChristophe Fergeau <cfergeau@redhat.com>2014-12-08 15:06:35 +0100
commit9f019d0cfdb2025e951ea4f8e81fc8a8b530518a (patch)
treed3add4ab8586c4fa92aa4ab8386ad1368d96fb62 /HACKING
parentf1271380381bb49b4a4c38950fe77a60d19ea9a3 (diff)
downloadlibvirt-9f019d0cfdb2025e951ea4f8e81fc8a8b530518a.tar.gz
docs: Use gender-neutral pronoun in hacking.html.in
Use 'they' instead of 'he'.
Diffstat (limited to 'HACKING')
-rw-r--r--HACKING12
1 files changed, 6 insertions, 6 deletions
diff --git a/HACKING b/HACKING
index 0be13bb86f..884e78cadd 100644
--- a/HACKING
+++ b/HACKING
@@ -61,12 +61,12 @@ Please follow this as close as you can, especially the rebase and git
send-email part, as it makes life easier for other developers to review your
patch set. One should avoid sending patches as attachments, but rather send
them in email body along with commit message. If a developer is sending
-another version of the patch (e.g. to address review comments), he is advised
-to note differences to previous versions after the "---" line in the patch so
-that it helps reviewers but doesn't become part of git history. Moreover, such
-patch needs to be prefixed correctly with "--subject-prefix=PATCHv2" appended
-to "git send-email" (substitute "v2" with the correct version if needed
-though).
+another version of the patch (e.g. to address review comments), they are
+advised to note differences to previous versions after the "---" line in the
+patch so that it helps reviewers but doesn't become part of git history.
+Moreover, such patch needs to be prefixed correctly with
+"--subject-prefix=PATCHv2" appended to "git send-email" (substitute "v2" with
+the correct version if needed though).