summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorpaul <paul>2005-04-05 10:14:50 +0000
committerpaul <paul>2005-04-05 10:14:50 +0000
commitd25640dce0ed0fa9f80c82e27f87fa9f2114e68c (patch)
tree4946d1eb1f7b5e535845835322d2af2d8695c4f9
parentfa3a166f6db67e602b9e895a8971caca0eb60da1 (diff)
downloadquagga-d25640dce0ed0fa9f80c82e27f87fa9f2114e68c.tar.bz2
quagga-d25640dce0ed0fa9f80c82e27f87fa9f2114e68c.tar.xz
2005-04-05 Paul Jakma <paul@dishone.st>
* HACKING: Expand on the importance of supplying good ChangeLog's in the PATCH SUBMISSION section.
-rw-r--r--ChangeLog3
-rw-r--r--HACKING4
2 files changed, 5 insertions, 2 deletions
diff --git a/ChangeLog b/ChangeLog
index 51dff528..33dc6242 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -2,7 +2,8 @@
* HACKING: remove the 'manually patch redhat/quagga.spec' bit
from RELEASE section. Let the rpm revision be CONFDATE, will work
- fine.
+ fine. Expand on the importance of supplying good ChangeLog's in
+ the PATCH SUBMISSION section.
2005-04-04 Hasso Tepper <hasso at quagga.net>
diff --git a/HACKING b/HACKING
index 55b92ae3..d86e55d3 100644
--- a/HACKING
+++ b/HACKING
@@ -113,7 +113,9 @@ PATCH SUBMISSION
cvs <cvs opts> diff -upwb ....
* Include ChangeLog and NEWS entries as appropriate before the patch
- (or in it if you are 100% up to date).
+ (or in it if you are 100% up to date). A good ChangeLog makes it easier to
+ review a patch, hence failure to include a good ChangeLog is prejudicial
+ to proper review of the patch, and hence the possibility of inclusion.
* Include only one semantic change or group of changes per patch.