From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner+akpm=40zip.com.au@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id <S315413AbSELUVb>; Sun, 12 May 2002 16:21:31 -0400
Received: (majordomo@vger.kernel.org) by vger.kernel.org
	id <S315414AbSELUVa>; Sun, 12 May 2002 16:21:30 -0400
Received: from parcelfarce.linux.theplanet.co.uk ([195.92.249.252]:60939 "EHLO
	www.linux.org.uk") by vger.kernel.org with ESMTP id <S315413AbSELUV3>;
	Sun, 12 May 2002 16:21:29 -0400
Message-ID: <3CDECE75.2000809@mandrakesoft.com>
Date: Sun, 12 May 2002 16:20:05 -0400
From: Jeff Garzik <jgarzik@mandrakesoft.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.9) Gecko/00200203
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Linus Torvalds <torvalds@transmeta.com>
CC: linux-kernel@vger.kernel.org
Subject: Re: Changelogs on kernel.org
In-Reply-To: <20020512010709.7a973fac.spyro@armlinux.org> <abmi0f$ugh$1@penguin.transmeta.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
X-Mailing-List: linux-kernel@vger.kernel.org

Linus Torvalds wrote:

>The 2.4.x changelogs seem to be done with my "release" scripts, but
>additionally they don't have the same kind of detailed information that
>the 2.5.x kernels have, and yes, the result is fairly ugly.
>
>What are peoples opinion about the "full" changelog format that v2.5.x
>kernels have? Should we sort that too by author?
>

Sorting might help a tiny bit...

I thought about this, when I saw the 2.4.x changelogs.  Typical GNU 
projects seem to have a pretty decent system going -- there is a 
detailed ChangeLog, and an abbreviated high level summary NEWS, for each 
release.

So IMO a good solution would not be to change the format of the BK 
changelogs, but to supplement them with the type of summary that looks 
like the "old Linus" changelogs, i.e. a summary generated by a human:

    Martin Dalecki - IDE updates
    Al Viro - VFS updates
    Andi Kleen - x86-64 update
    ...

The central complaint about BK changelogs seems to be that they are too 
verbose for a quick scan of what a new kernel version contains.  (while 
at the same time lauding the additional information BK provides over the 
old changelogs)

Marcelo gave it a good shot, by (it appears) generating a summary by 
taking the first line of each cset.  The better solution would be a 
human-generated NEWS file.

    Jeff