External/libvirt
1
0
Fork 0
mirror of https://gitlab.com/libvirt/libvirt.git synced 2025-02-22 11:22:23 +00:00
Code Issues Packages Projects Releases Wiki Activity

docs: Use gender-neutral pronoun in hacking.html.in

Browse Source 
Use 'they' instead of 'he'.
This commit is contained in:
Christophe Fergeau 2014-12-08 14:13:00 +01:00
parent f127138038
commit 9f019d0cfd
2 changed files with 7 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
HACKING
View File

@ -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 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 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 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 another version of the patch (e.g. to address review comments), they are
to note differences to previous versions after the "---" line in the patch so advised to note differences to previous versions after the "---" line in the
that it helps reviewers but doesn't become part of git history. Moreover, such patch so that it helps reviewers but doesn't become part of git history.
patch needs to be prefixed correctly with "--subject-prefix=PATCHv2" appended Moreover, such patch needs to be prefixed correctly with
to "git send-email" (substitute "v2" with the correct version if needed "--subject-prefix=PATCHv2" appended to "git send-email" (substitute "v2" with
though). the correct version if needed though).

2
docs/hacking.html.in
View File

@ -65,7 +65,7 @@
review your patch set. One should avoid sending patches as attachments, review your patch set. One should avoid sending patches as attachments,
but rather send them in email body along with commit message. If a 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 developer is sending another version of the patch (e.g. to address
review comments), he is advised to note differences to previous review comments), they are advised to note differences to previous
versions after the <code>---</code> line in the patch so that it helps versions after the <code>---</code> line in the patch so that it helps
reviewers but doesn't become part of git history. Moreover, such patch reviewers but doesn't become part of git history. Moreover, such patch
needs to be prefixed correctly with needs to be prefixed correctly with