Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757357AbXIUMvh (ORCPT ); Fri, 21 Sep 2007 08:51:37 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1757386AbXIUMv1 (ORCPT ); Fri, 21 Sep 2007 08:51:27 -0400 Received: from cerber.ds.pg.gda.pl ([153.19.208.18]:40809 "EHLO cerber.ds.pg.gda.pl" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755212AbXIUMvZ (ORCPT ); Fri, 21 Sep 2007 08:51:25 -0400 Date: Fri, 21 Sep 2007 13:51:12 +0100 (BST) From: "Maciej W. Rozycki" To: Andrew Morton cc: Andy Fleming , Jeff Garzik , netdev@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH] PHYLIB: IRQ event workqueue handling fixes In-Reply-To: <20070920165348.0b25be3d.akpm@linux-foundation.org> Message-ID: References: <20070920165348.0b25be3d.akpm@linux-foundation.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1098 Lines: 26 On Thu, 20 Sep 2007, Andrew Morton wrote: > You always put boring, crappy, insufficient text in the for-the-changelog > section and interesting, useful, sufficient text in the not-for-the-changelog > section. I'll swap the sections in the future then. ;-) Frankly I was not sure whether the changelog was happy about being fed with lengthy explanations and it has not spoken out. I have to admit this is a habit carried over from the FSF-style ChangeLog -- where the enforced rule is actually *not* to provide any explanation for why changes are done and only describe what has been modified (with any discussion around archived in the respective mailing list). > But you can't fool me! I have an editor and I fix it up. Thank you and sorry for the extra work I caused you -- I shall keep your suggestion in mind in the future. Maciej - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/