[Xen-devel] Re: API Changelog

To:	John Levon <levon@xxxxxxxxxxxxxxxxx>
Subject:	[Xen-devel] Re: API Changelog
From:	Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Date:	Mon, 07 Jan 2008 17:47:21 +0000
Cc:	xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date:	Mon, 07 Jan 2008 09:47:48 -0800
Envelope-to:	www-data@xxxxxxxxxxxxxxxxxx
In-reply-to:	<20080107162233.GA19323@xxxxxxxxxxxxxxxxxxxxxxx>
List-help:	<mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id:	Xen developer discussion <xen-devel.lists.xensource.com>
List-post:	<mailto:xen-devel@lists.xensource.com>
List-subscribe:	<http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe:	<http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender:	xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index:	AchRVVpamL4dIL1IEdyexQAWy6hiGQ==
Thread-topic:	API Changelog
User-agent:	Microsoft-Entourage/11.3.6.070618

View the file with 'hg annotate'?

 -- Keir

On 7/1/08 16:22, "John Levon" <levon@xxxxxxxxxxxxxxxxx> wrote:

> 
> Now I remember why I didn't want a file in the source tree. There's
> absolutely no sensible way to have any entries there that give a
> meaningful link to the actual details - you can't link to the rev until
> it's merged, and you can't commit until the rev is written in it.
> 
> The only other option is dates which is way too vague (date when the
> patch was written is a really poor indicator of when the change got
> merged).
> 
> I guess keywords would help, except mercurial doesn't do them. Keir?
> 
> regards
> john



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

WARNING - OLD ARCHIVES

xen-devel

[Xen-devel] Re: API Changelog