From: "S.Çağlar Onur" <caglar@pardus.org.tr>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: xen-devel@lists.xensource.com,
"Daniel P. Berrange" <berrange@redhat.com>
Subject: Re: 3.1.x and 3.2.x releases
Date: Tue, 1 Jan 2008 18:31:31 +0200 [thread overview]
Message-ID: <200801011831.34865.caglar@pardus.org.tr> (raw)
In-Reply-To: <C39ACE33.11984%Keir.Fraser@cl.cam.ac.uk>
[-- Attachment #1.1: Type: text/plain, Size: 1036 bytes --]
Hi;
28 Ara 2007 Cum tarihinde, Keir Fraser şunları yazmıştı:
> Well, I hopefully fixed it now anyway, both in 3.1-testing and unstable.
Although xen-unstable has following
caglar@zangetsu xen-unstable.hg $ hg log -r ad0f20f5590a
changeset: 16674:ad0f20f5590a
user: Keir Fraser <keir.fraser@citrix.com>
date: Fri Dec 28 15:44:51 2007 +0000
summary: Rename uintN_t guest handles to uintN, to avoid nameclash with
uintN_t
3.1-testing still not updated,
caglar@zangetsu xen-3.1-testing.hg $ hg log -r tip
changeset: 15564:9093b433fa5c
tag: tip
user: Keir Fraser <keir.fraser@citrix.com>
date: Thu Dec 20 14:57:03 2007 +0000
summary: xend: Clean up hvm_build Python wrapper. Python code can get/set
hvm
Did you forgot to push or 3.1-testing commits waits for internal testing?
Cheers
--
S.Çağlar Onur <caglar@pardus.org.tr>
http://cekirdek.pardus.org.tr/~caglar/
Linux is like living in a teepee. No Windows, no Gates and an Apache in house!
[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2008-01-01 16:31 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-19 16:00 3.1.x and 3.2.x releases Keir Fraser
2007-12-19 17:22 ` Dan Magenheimer
2007-12-20 10:26 ` Keir Fraser
2007-12-26 19:53 ` Dan Magenheimer
2007-12-26 23:08 ` Keir Fraser
2007-12-28 22:52 ` Dan Magenheimer
2007-12-29 9:18 ` Keir Fraser
2007-12-29 9:21 ` Keir Fraser
2008-01-03 17:24 ` Dan Magenheimer
2007-12-19 18:34 ` John Levon
2007-12-20 3:58 ` You, Yongkang
2007-12-20 5:02 ` John Levon
2007-12-27 23:37 ` S.Çağlar Onur
2007-12-28 8:38 ` Keir Fraser
2007-12-28 10:17 ` S.Çağlar Onur
2007-12-28 13:16 ` Keir Fraser
2007-12-28 14:55 ` John Levon
2007-12-28 15:19 ` Keir Fraser
2007-12-29 1:18 ` Ryan Scott
2007-12-28 15:47 ` Daniel P. Berrange
2007-12-28 16:00 ` Keir Fraser
2008-01-01 16:31 ` S.Çağlar Onur [this message]
2008-01-06 22:50 ` Keir Fraser
2007-12-28 23:04 ` S.Çağlar Onur
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=200801011831.34865.caglar@pardus.org.tr \
--to=caglar@pardus.org.tr \
--cc=Keir.Fraser@cl.cam.ac.uk \
--cc=berrange@redhat.com \
--cc=xen-devel@lists.xensource.com \
/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.