From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ben Guthro Subject: Re: API Changelog Date: Mon, 07 Jan 2008 11:30:28 -0500 Message-ID: <478253A4.20707@virtualiron.com> References: <20080107162233.GA19323@totally.trollied.org.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20080107162233.GA19323@totally.trollied.org.uk> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: John Levon Cc: xen-devel List-Id: xen-devel@lists.xenproject.org It does via an extension: http://www.selenic.com/mercurial/wiki/index.cgi/KeywordExpansionExtension http://osdir.com/ml/os.solaris.opensolaris.tools.general/2006-05/msg00167.html John Levon 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@lists.xensource.com > http://lists.xensource.com/xen-devel >