From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from [140.186.70.92] (port=42075 helo=eggs.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1Phjzz-0004uO-SA
	for qemu-devel@nongnu.org; Tue, 25 Jan 2011 09:36:00 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <anthony@codemonkey.ws>) id 1Phjzy-00015n-NW
	for qemu-devel@nongnu.org; Tue, 25 Jan 2011 09:35:59 -0500
Received: from mail-yx0-f173.google.com ([209.85.213.173]:44310)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <anthony@codemonkey.ws>) id 1Phjzy-00015f-DE
	for qemu-devel@nongnu.org; Tue, 25 Jan 2011 09:35:58 -0500
Received: by yxl31 with SMTP id 31so1971175yxl.4
	for <qemu-devel@nongnu.org>; Tue, 25 Jan 2011 06:35:57 -0800 (PST)
Message-ID: <4D3EDFCC.7020609@codemonkey.ws>
Date: Tue, 25 Jan 2011 08:35:56 -0600
From: Anthony Liguori <anthony@codemonkey.ws>
MIME-Version: 1.0
Subject: Re: [Qemu-devel] git rm Changelog?
References: <ihl0l5$mvm$1@dough.gmane.org> <4D3E9E7F.5080207@redhat.com>
In-Reply-To: <4D3E9E7F.5080207@redhat.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Kevin Wolf <kwolf@redhat.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>, qemu-devel@nongnu.org

On 01/25/2011 03:57 AM, Kevin Wolf wrote:
> Am 25.01.2011 00:06, schrieb Paolo Bonzini:
>    
>> ... or at least "git mv Changelog Changelog.old"?
>>
>> It only goes back to 0.12.0 so that there is hardly a place in the git
>> repo to look for new features in 0.13 and 0.14.
>>      
> Or maybe update it?
>
> I find it rather unfriendly to our users to say "Here is a new release.
> In the unlikely case that you really want to know what has changed,
> please bother yourself to filter the interesting stuff out of these
> thousand git commits".
>    

Logistically, I prefer doing highlights in a mail verses having a 
committed file.  A Changelog file needs to be committed prior to tagging 
a release and cannot be enhanced after the fact.  The nice bit about an 
email is that folks can respond to it with additional details.

A wiki page (similar to what kernel newbies does) would be nice to 
supplement what's included in the release notes.

Regards,

Anthony Liguori

> Kevin
>
>