diff options
author | Christophe Fergeau <cfergeau@redhat.com> | 2014-12-08 14:13:00 +0100 |
---|---|---|
committer | Christophe Fergeau <cfergeau@redhat.com> | 2014-12-08 15:06:35 +0100 |
commit | 9f019d0cfdb2025e951ea4f8e81fc8a8b530518a (patch) | |
tree | d3add4ab8586c4fa92aa4ab8386ad1368d96fb62 /HACKING | |
parent | f1271380381bb49b4a4c38950fe77a60d19ea9a3 (diff) | |
download | libvirt-9f019d0cfdb2025e951ea4f8e81fc8a8b530518a.tar.gz |
docs: Use gender-neutral pronoun in hacking.html.in
Use 'they' instead of 'he'.
Diffstat (limited to 'HACKING')
-rw-r--r-- | HACKING | 12 |
1 files changed, 6 insertions, 6 deletions
@@ -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). |