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-users] Re: correct procedure for reporting kernel problems?

To: "Ian P. Christian" <pookey@xxxxxxxxxxxx>
Subject: Re: [Xen-users] Re: correct procedure for reporting kernel problems?
From: Charles Duffy <cduffy@xxxxxxxxxxx>
Date: Sat, 19 Nov 2005 14:45:52 -0600
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Sat, 19 Nov 2005 20:46:36 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <200511192033.01320.pookey@xxxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <200511191828.20811.pookey@xxxxxxxxxxxx> <dlnvsf$dpp$1@xxxxxxxxxxxxx> <200511192033.01320.pookey@xxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird 1.4 (Windows/20050908)
Ian P. Christian wrote:
On Saturday 19 November 2005 19:53, Charles Duffy wrote:
One request -- please specify a changeset number instead of just saying
"the latest unstable". I've seen an issue much like you're reporting,
but it was fixed for me some time ago. Knowing exactly how current the
"latest unstable" you're using is is useful in such cases.

appologies, I'm not at all familiar with the versioning control program, how do I tell? 'hg status' seemed like the most likely command in the man page, but that does't show me anyhting of help.
"hg identify" will show precisely the changeset you're using (though by its hash value rather than by number). The output of "hg log" will start with the most recent known changeset, and by searching for the hash from "hg identify" in the "hg log" output you can determine exactly what you're running. So long as you did an update after your pull, you should generally be on the first changeset in the "hg log" output.

Xen-users mailing list