From: Nitin Kamble <nkamble@gmail.com>
To: Ian Pratt <ian.pratt@cl.cam.ac.uk>,
Keir Fraser <keir.fraser@cl.cam.ac.uk>,
Grzesiek <gm281@hermes.cam.ac.uk>
Cc: xen-devel@lists.sourceforge.net
Subject: Re: xend start - failing ...
Date: Wed, 22 Sep 2004 16:26:02 -0700 [thread overview]
Message-ID: <2d12b183040922162662d8d984@mail.gmail.com> (raw)
In-Reply-To: <E1CADvK-0000rL-00@mta1.cl.cam.ac.uk>
Thanks a lot Ian, Keir & Grzesiek for the update.
Regards,
Nitin
On Wed, 22 Sep 2004 21:41:09 +0100, Ian Pratt <ian.pratt@cl.cam.ac.uk> wrote:
> > Thanks Ian.
> >
> > One more questions,
> > What is the difference in xeno-unstable.bk and xen-2.0.bk ?
>
> Right now, nothing.
>
> We're currently undergoing a feature freeze in the unstable tree,
> so the 2.0 tree is typically just a slightly time-delayed version
> of the unstable tree. We typically test stuff in the unstable
> tree for a couple of days then push it out to 2.0 if there are no
> problems reported.
>
> After the official 2.0 release you can expect them to diverge
> again, as the unstable tree undergoes changes for SMP guests and
> a couple of other major projects we have planned.
>
> Ian
>
-------------------------------------------------------
This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170
Project Admins to receive an Apple iPod Mini FREE for your judgement on
who ports your project to Linux PPC the best. Sponsored by IBM.
Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php
prev parent reply other threads:[~2004-09-22 23:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-22 19:12 xend start - failing Nitin Kamble
2004-09-22 19:46 ` Keir Fraser
2004-09-22 19:53 ` Ian Pratt
2004-09-22 20:10 ` Nitin Kamble
2004-09-22 20:41 ` Ian Pratt
2004-09-22 23:26 ` Nitin Kamble [this message]
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=2d12b183040922162662d8d984@mail.gmail.com \
--to=nkamble@gmail.com \
--cc=gm281@hermes.cam.ac.uk \
--cc=ian.pratt@cl.cam.ac.uk \
--cc=keir.fraser@cl.cam.ac.uk \
--cc=xen-devel@lists.sourceforge.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.