From mboxrd@z Thu Jan 1 00:00:00 1970 From: aq Subject: Re: xen-unstable-src tarball Date: Fri, 1 Jul 2005 23:41:34 +0900 Message-ID: <9cde8bff05070107412374ff5e@mail.gmail.com> References: <1120221252.11716.17.camel@crusher.takatukaland.de> <9cde8bff0507010709388b1157@mail.gmail.com> <1120228367.11716.36.camel@crusher.takatukaland.de> Reply-To: aq Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <1120228367.11716.36.camel@crusher.takatukaland.de> Content-Disposition: inline List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Nils Toedtmann Cc: Ian Pratt , xen-devel List-Id: xen-devel@lists.xenproject.org On 7/1/05, Nils Toedtmann wrote: > Am Freitag, den 01.07.2005, 23:09 +0900 schrieb aq: > > On 7/1/05, Nils Toedtmann wrote: > > > > > > Btw: "xm dmesg" shows > > > > > > Latest ChangeSet: information unavailable > > > > This is not a bug, if you are running stable version. The tree of > > stable is not BK repo itself, so there is no changeset notation. >=20 > I use the testing/unstable snapshot tarballs. >=20 > > But if you use bk to pull the unstable or testing version to your > > machine, then compile it, the "Last ChangeSet" will be shown (of > > course your machine must install bk) >=20 > So there is a piece of bk/hg-metainformation not in the snapshots. >=20 indeed. all the SCM metainformation is removed in all the snapshots. so that "Latest Changeset" will not be shown if you dont get the code from repo. lets consider that information is for developers only ;-) regards, aq