From: Christoph Egger <Christoph.Egger@amd.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: xen-devel@lists.xensource.com, Dulloor <dulloor@gmail.com>
Subject: Re: xen compilation error
Date: Thu, 22 Jan 2009 13:53:49 +0100 [thread overview]
Message-ID: <200901221353.50124.Christoph.Egger@amd.com> (raw)
In-Reply-To: <18808.25803.924748.804103@mariner.uk.xensource.com>
On Thursday 22 January 2009 13:21:31 Ian Jackson wrote:
> Christoph Egger writes ("Re: [Xen-devel] xen compilation error"):
> > This sort of problem can only happen with nested repositories.
> > (Makes also hard to make snapshots.)
> > Can we have ioemu back in the mercurial tree, please?
>
> I'm afraid it's not really practical to do the necessary
> upstream-tracking and multiple branches with hg, particularly given
> that almost everyone else in the qemu world is using git.
qemu uses subversion and so do I.
Handling patches with mercurial is easy with the pbranch extension:
http://arrenbrecht.ch/mercurial/pbranch/
> If you don't like the nested repositories, you can have side-by-side
> repositories by setting CONFIG_QEMU in .config (or wherever else you
> like to set things).
>
> Alternatively, we could provide a
> make update
> at the top-level of xen-unstable.hg which updated qemu too ?
That's nice. Also a 'make snapshot' or 'make archive' would be handy to
quickly make a tarball.
--
---to satisfy European Law for business letters:
Advanced Micro Devices GmbH
Karl-Hammerschmidt-Str. 34, 85609 Dornach b. Muenchen
Geschaeftsfuehrer: Jochen Polster, Thomas M. McCoy, Giuliano Meroni
Sitz: Dornach, Gemeinde Aschheim, Landkreis Muenchen
Registergericht Muenchen, HRB Nr. 43632
next prev parent reply other threads:[~2009-01-22 12:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-21 18:00 xen compilation error Dulloor
2009-01-21 18:14 ` Keir Fraser
2009-01-22 12:03 ` Ian Jackson
2009-01-22 12:13 ` Christoph Egger
2009-01-22 12:21 ` Ian Jackson
2009-01-22 12:53 ` Christoph Egger [this message]
2009-01-22 19:54 ` Dulloor
2009-01-26 11:01 ` Ian Jackson
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=200901221353.50124.Christoph.Egger@amd.com \
--to=christoph.egger@amd.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=dulloor@gmail.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.