summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorpaul <paul>2004-05-13 13:38:06 +0000
committerpaul <paul>2004-05-13 13:38:06 +0000
commitd184e020dc6e377fbc4e99770e640683ffad360f (patch)
tree7485060b7da94d5fd9a2e6988d17fa86a1d2e6f3
parenta298b7e1f238c4faa4fbac61ed76fe547acd001f (diff)
downloadquagga-d184e020dc6e377fbc4e99770e640683ffad360f.tar.bz2
quagga-d184e020dc6e377fbc4e99770e640683ffad360f.tar.xz
2004-05-13 Paul Jakma <paul@dishone.st>
* HACKING: Add comment about updating ChangeLogs (which this commit, ironically, hasnt neglected to do).
-rw-r--r--HACKING3
1 files changed, 3 insertions, 0 deletions
diff --git a/HACKING b/HACKING
index 3f62eb88..30565f21 100644
--- a/HACKING
+++ b/HACKING
@@ -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).