summaryrefslogtreecommitdiff
path: root/HACKING
diff options
context:
space:
mode:
authorpaul <paul>2004-05-13 13:38:06 +0000
committerpaul <paul>2004-05-13 13:38:06 +0000
commit4134ceb7f4a5177e90e77668ec1e1d2b8a17ea72 (patch)
tree2a26a1df33384806d8f852bbe4545fb5422aba49 /HACKING
parentf88258c8386a6a5f4a7a7994a1d3a34ab0ef244b (diff)
2004-05-13 Paul Jakma <paul@dishone.st>
* HACKING: Add comment about updating ChangeLogs (which this commit, ironically, hasnt neglected to do).
Diffstat (limited to 'HACKING')
-rw-r--r--HACKING5
1 files changed, 4 insertions, 1 deletions
diff --git a/HACKING b/HACKING
index 9fe61dee..1ffdab87 100644
--- a/HACKING
+++ b/HACKING
@@ -1,6 +1,6 @@
-*- mode: text; -*-
-$Id: HACKING,v 1.5 2004/01/09 16:34:54 paul Exp $
+$Id: HACKING,v 1.6 2004/05/13 13:38:06 paul Exp $
GUIDELINES FOR HACKING ON QUAGGA
@@ -63,6 +63,9 @@ PATCH APPLICATION TO CVS
* If the patch might break something, issue a call for testing on the
mailinglist.
+* Give an appropriate commit message, eg the ChangeLog entry should suffice,
+ if it does not, then the ChangeLog entry itself needs to be corrected.
+
* By committing a patch, you are responsible for fixing problems
resulting from it (or backing it out).