public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Christian Borntraeger <borntraeger@de.ibm.com>
To: Gleb Natapov <gleb@redhat.com>
Cc: kvm@vger.kernel.org, Alexander Graf <agraf@suse.de>,
	mtosatti@redhat.com, Cornelia Huck <cornelia.huck@de.ibm.com>
Subject: Re: kvm.git:next branch is going to be frozen shortly for 3.9 merge
Date: Mon, 11 Feb 2013 09:39:29 +0100	[thread overview]
Message-ID: <5118AE41.5040501@de.ibm.com> (raw)
In-Reply-To: <20130210135054.GS7837@redhat.com>

On 10/02/13 14:50, Gleb Natapov wrote:
> As 3.8 release is inevitably going closer next branch is going to be
> frozen this week. All new patches will be applied to queue only awaiting
> for the 3.9-rc1. If you have something for 3.8 please send it asap.

Please consider 

"s390: Fix handling of iscs" for the initial virtio-ccw merge. (I assume
its planned for 3.9-rc1)

Christian


      parent reply	other threads:[~2013-02-11  8:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-10 13:50 kvm.git:next branch is going to be frozen shortly for 3.9 merge Gleb Natapov
2013-02-10 23:35 ` Alexander Graf
2013-02-11  8:39 ` Christian Borntraeger [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=5118AE41.5040501@de.ibm.com \
    --to=borntraeger@de.ibm.com \
    --cc=agraf@suse.de \
    --cc=cornelia.huck@de.ibm.com \
    --cc=gleb@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=mtosatti@redhat.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