WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

[Xen-devel] API Changelog

To: Keir.Fraser@xxxxxxxxxxxx
Subject: [Xen-devel] API Changelog
From: John Levon <levon@xxxxxxxxxxxxxxxxx>
Date: Mon, 7 Jan 2008 16:22:33 +0000
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Mon, 07 Jan 2008 08:23:19 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
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
User-agent: Mutt/1.5.9i
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