From mboxrd@z Thu Jan  1 00:00:00 1970
From: Marcelo Tosatti <mtosatti@redhat.com>
Subject: stable tag on kvm patches
Date: Fri, 16 Apr 2010 17:59:01 -0300
Message-ID: <20100416205901.GA22144@amt.cnet>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: Avi Kivity <avi@redhat.com>, Anthony Liguori <aliguori@us.ibm.com>
To: kvm <kvm@vger.kernel.org>
Return-path: <kvm-owner@vger.kernel.org>
Received: from mx1.redhat.com ([209.132.183.28]:60906 "EHLO mx1.redhat.com"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S932414Ab0DPU7N (ORCPT <rfc822;kvm@vger.kernel.org>);
	Fri, 16 Apr 2010 16:59:13 -0400
Content-Disposition: inline
Sender: kvm-owner@vger.kernel.org
List-ID: <kvm.vger.kernel.org>


To have better testing over -stable kernel KVM Avi decided to drop
the Cc: stable@kernel.org tag (which meant such patches are included
directly in the process by Greg), to instead queue patches in
kvm-updates/2.6.3x branches and autotest them before submission.

So to avoid automatic inclusion, a new tag for stable patches
is proposed: KVM-Stable-Tag. Please use that instead of "Cc:
stable@kernel.org".

BTW, this could also be useful to help the cherry-picking
process for qemu/qemu-kvm stable branches.