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/
Home Products Support Community News


Re: [Xen-devel] xen-unstable-src tarball

To: Nils Toedtmann <xen-devel@xxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] xen-unstable-src tarball
From: aq <aquynh@xxxxxxxxx>
Date: Fri, 1 Jul 2005 23:41:34 +0900
Cc: Ian Pratt <m+Ian.Pratt@xxxxxxxxxxxx>, xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Fri, 01 Jul 2005 14:40:24 +0000
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=ASDZKiHRVJVI59yJfJQI9uSumPlSFIUK/I1vBpBQ55ocSoDQApkwlJ30J+DtOSlQ/0nbtdWIWn3GF3zSKinVvjuBdpvwQkl939TpUQ1i9AkHttZtXzGhuHb+dtpnlEQdafTC0v2d9XHWM+Vmc93CCnpVGAu5Fct6SrU0hpR4xO4=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <1120228367.11716.36.camel@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>
References: <A95E2296287EAD4EB592B5DEEFCE0E9D28249E@xxxxxxxxxxxxxxxxxxxxxxxxxxx> <1120221252.11716.17.camel@xxxxxxxxxxxxxxxxxxxxxxx> <9cde8bff0507010709388b1157@xxxxxxxxxxxxxx> <1120228367.11716.36.camel@xxxxxxxxxxxxxxxxxxxxxxx>
Reply-to: aq <aquynh@xxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On 7/1/05, Nils Toedtmann <xen-devel@xxxxxxxxxxxxxxxxxx> wrote:
> Am Freitag, den 01.07.2005, 23:09 +0900 schrieb aq:
> > On 7/1/05, Nils Toedtmann <xen-devel@xxxxxxxxxxxxxxxxxx> 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.
> I use the testing/unstable snapshot tarballs.
> > 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)
> So there is a piece of bk/hg-metainformation not in the snapshots.

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 ;-)


Xen-devel mailing list