From: Christoph Egger <Christoph.Egger@amd.com>
To: xen-devel@lists.xensource.com
Subject: ioemu
Date: Mon, 1 Sep 2008 11:23:17 +0200 [thread overview]
Message-ID: <200809011123.17339.Christoph.Egger@amd.com> (raw)
Hi,
is it possible to get ioemu-remote into mercurial?
When I packaged Xen 3.3.0 for NetBSD, I run into the problem that
the git tree could not checked against a checksum because
a) the download happens during the build phase.
b) the checksum check works against one file but not against a whole tree
The checksum phase happens right after the download of the
Xen 3.3.0 source tarball.
I think, Gentoo Linux has the same problem.
I worked around this by using the in-tree ioemu.
In this respect, I would like to know if the move to the new ioemu can be done
by updating the ioemu code in the mercurial tree by taking over the sources
from the ioemu-remote tree into mercural tree.
This would also allow to create snapshot packages from unstable
via hg archive -t tgz xen-snapshot.tar.gz in a half-automated way.
Christoph
--
AMD Saxony, Dresden, Germany
Operating System Research Center
Legal Information:
AMD Saxony Limited Liability Company & Co. KG
Sitz (Geschäftsanschrift):
Wilschdorfer Landstr. 101, 01109 Dresden, Deutschland
Registergericht Dresden: HRA 4896
vertretungsberechtigter Komplementär:
AMD Saxony LLC (Sitz Wilmington, Delaware, USA)
Geschäftsführer der AMD Saxony LLC:
Dr. Hans-R. Deppe, Thomas McCoy
next reply other threads:[~2008-09-01 9:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-01 9:23 Christoph Egger [this message]
2008-09-01 10:05 ` ioemu Ian Jackson
2008-09-01 11:34 ` ioemu Christoph Egger
2008-09-01 12:16 ` ioemu Ian Jackson
2008-09-01 15:00 ` ioemu Christoph Egger
2008-09-01 15:10 ` ioemu Ian Jackson
2008-09-01 12:18 ` ioemu Ian Pratt
2008-09-01 12:50 ` ioemu John Levon
2008-09-01 17:06 ` ioemu Brendan Cully
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=200809011123.17339.Christoph.Egger@amd.com \
--to=christoph.egger@amd.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.