From: aq <aquynh@gmail.com>
To: Nils Toedtmann <xen-devel@nils.toedtmann.net>
Cc: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>,
xen-devel <xen-devel@lists.xensource.com>
Subject: Re: xen-unstable-src tarball
Date: Fri, 1 Jul 2005 23:41:34 +0900 [thread overview]
Message-ID: <9cde8bff05070107412374ff5e@mail.gmail.com> (raw)
In-Reply-To: <1120228367.11716.36.camel@crusher.takatukaland.de>
On 7/1/05, Nils Toedtmann <xen-devel@nils.toedtmann.net> wrote:
> Am Freitag, den 01.07.2005, 23:09 +0900 schrieb aq:
> > On 7/1/05, Nils Toedtmann <xen-devel@nils.toedtmann.net> 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 ;-)
regards,
aq
next prev parent reply other threads:[~2005-07-01 14:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-01 12:10 xen-unstable-src tarball Ian Pratt
2005-07-01 12:34 ` Nils Toedtmann
2005-07-01 14:09 ` aq
2005-07-01 14:32 ` Nils Toedtmann
2005-07-01 14:41 ` aq [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-07-04 21:59 Ian Pratt
2005-07-01 11:54 Nils Toedtmann
2005-07-01 13:49 ` wei huang
2005-07-01 14:28 ` Nils Toedtmann
2005-07-04 21:24 ` Frank Heydlauf
2005-07-04 21:27 ` Mark A. Williamson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9cde8bff05070107412374ff5e@mail.gmail.com \
--to=aquynh@gmail.com \
--cc=m+Ian.Pratt@cl.cam.ac.uk \
--cc=xen-devel@lists.xensource.com \
--cc=xen-devel@nils.toedtmann.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.