From 6a52470660000bb6ddba971dc5c40b3422ab49bc Mon Sep 17 00:00:00 2001 From: paul Date: Tue, 5 Apr 2005 10:14:50 +0000 Subject: 2005-04-05 Paul Jakma * HACKING: Expand on the importance of supplying good ChangeLog's in the PATCH SUBMISSION section. --- ChangeLog | 3 ++- HACKING | 6 ++++-- 2 files changed, 6 insertions(+), 3 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 diff --git a/HACKING b/HACKING index 07e5c62a..6f3e03b2 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 @@ PATCH SUBMISSION cvs 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. -- cgit v1.2.1