[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
update HACKING file
From: |
Ben Elliston |
Subject: |
update HACKING file |
Date: |
Wed, 25 Nov 2015 21:08:19 +1100 |
User-agent: |
Mutt/1.5.23 (2014-03-12) |
Fairly obvious.
Cheers, Ben
---
HACKING | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/HACKING b/HACKING
index 0005988..a894e1d 100644
--- a/HACKING
+++ b/HACKING
@@ -18,8 +18,8 @@ If a change fixes a test, mention the test in the ChangeLog
entry.
To this end, the Autotest-mode is handy.
** Bug reports
-If somebody reports a new bug, mention his name in the ChangeLog entry
-and in the test case you write. Put him into THANKS.
+If somebody reports a new bug, mention their name in the ChangeLog
+entry and in the test case you write. Put them into THANKS.
The correct response to most actual bugs is to write a new test case
which demonstrates the bug. Then fix the bug, re-run the test suite,
--
1.9.1
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- update HACKING file,
Ben Elliston <=