xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: "Jan Beulich" <JBeulich@novell.com>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: master branch of xen.git
Date: Wed, 11 Aug 2010 07:38:33 +0100	[thread overview]
Message-ID: <4C626189020000780000F382@vpn.id2.novell.com> (raw)

Jeremy,

what's the disposition of the master branch of that tree? It doesn't
seem to have seen any update during the last couple of months,
and it's still 2.6.31-based. Shouldn't this be either what "stable"
is currently (i.e. 2.6.32-based) or match up with Linus' tree (or
the latest released version thereof)?

Jan

             reply	other threads:[~2010-08-11  6:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-11  6:38 Jan Beulich [this message]
2010-08-11  6:45 ` master branch of xen.git Jeremy Fitzhardinge
2010-08-11  6:58   ` Jan Beulich
2010-08-13  0:46     ` Jeremy Fitzhardinge

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=4C626189020000780000F382@vpn.id2.novell.com \
    --to=jbeulich@novell.com \
    --cc=jeremy@goop.org \
    --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).