From mboxrd@z Thu Jan  1 00:00:00 1970
From: Agostino Sarubbo <ago@gentoo.org>
Subject: security bugs and release
Date: Tue, 25 Jun 2013 19:07:14 +0200
Message-ID: <2052847.SzM2x6sscC@devil>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xen.org>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xen.org>
List-Help: <mailto:xen-devel-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=subscribe>
Sender: xen-devel-bounces@lists.xen.org
Errors-To: xen-devel-bounces@lists.xen.org
To: xen-devel@lists.xen.org
List-Id: xen-devel@lists.xenproject.org

Hello,

I'd like to know why when there is a new advisory you just release a patch 
instead of a new release.

This, in my opinion creates only confusion. For example, if I'm running 4.2.1 
I don't exatly know which patches have been applied. If you say, this is fixed 
in 4.2.2 I know that if I'm run that version, I'm fine.

Is there a real reason because you don't make a new release?
-- 
Agostino Sarubbo
Gentoo Linux Developer