commit 6a52470660000bb6ddba971dc5c40b3422ab49bc
author paul <paul> Tue Apr 05 10:14:50 2005 +0000
committer paul <paul> Tue Apr 05 10:14:50 2005 +0000
tree 76d2b5766fbe5cd105c09f938d35a151725db8ca
parent 208f0b7e73d8543b03297b74e3893e2c12735963

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

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

HACKING

diff --git a/HACKING b/HACKING
index 07e5c62..6f3e03b 100644
--- 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 @@
   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.