From: "Jan Beulich" <JBeulich@novell.com>
To: Keir Fraser <keir.fraser@eu.citrix.com>
Cc: Frank Van Der Linden <frank.van.der.linden@oracle.com>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: xen-unstable.hg not being updated?
Date: Mon, 19 Apr 2010 09:03:25 +0100 [thread overview]
Message-ID: <4BCC2A6D020000780003ACBD@vpn.id2.novell.com> (raw)
In-Reply-To: <C7F0F165.11A4C%keir.fraser@eu.citrix.com>
>>> Keir Fraser <keir.fraser@eu.citrix.com> 18.04.10 18:27 >>>
>There's a staging tree at
>http://xenbits.xensource.com/staging/xen-unstable.hg which will have all
>changesets in it. This gets pushed to the main tree when it passes automated
>regression tests.
In that respect - what about the linux-2.6.18 tree? Does this still get
automatically get pushed (c/s 1012 has been stuck in that tree for
several days, with -unstable since having seen a couple of pushes).
Jan
next prev parent reply other threads:[~2010-04-19 8:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-16 14:33 xen-unstable.hg not being updated? Frank Van Der Linden
2010-04-18 16:27 ` Keir Fraser
2010-04-19 8:03 ` Jan Beulich [this message]
2010-04-19 9:29 ` Keir Fraser
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=4BCC2A6D020000780003ACBD@vpn.id2.novell.com \
--to=jbeulich@novell.com \
--cc=frank.van.der.linden@oracle.com \
--cc=keir.fraser@eu.citrix.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).