2005-04-05 Paul Jakma <paul@dishone.st>

	* HACKING: Expand on the importance of supplying good ChangeLog's in
	  the PATCH SUBMISSION section.

diff --git a/ChangeLog b/ChangeLog
index 51dff528e8f30893b631f7fe048cac50a335cd7d..33dc6242a93d261664ee1e076416daf7b3771e9a 100644 (file)
--- 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 07e5c62a2c43c27f3655da1ffc5f1114241b85e0..6f3e03b2c725ac0923e3e96e7133e3fc48eb586b 100644 (file)
--- a/HACKING
+++ b/HACKING
@@ -1,5 +1,5 @@
 -*- mode: text; -*-
-$Id: HACKING,v 1.17 2005/04/05 10:10:06 paul Exp $
+$Id: HACKING,v 1.18 2005/04/05 10:14:50 paul Exp $
 
 GUIDELINES FOR HACKING ON QUAGGA
 
@@ -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.