From: Keir Fraser Subject: Re: [PATCH 0 of 4 v2] blkif.h: Document protocol and existing extensions Date: Wed, 15 Feb 2012 17:11:13 +0000 Message-ID: References: <4F3BBE3F02000078000732C6@nat28.tlf.novell.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <4F3BBE3F02000078000732C6@nat28.tlf.novell.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Jan Beulich , "Justin T. Gibbs" Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org On 15/02/2012 13:16, "Jan Beulich" wrote: >>> Why? It got bumped very recently to 0x040200, your change could >>> well go under that same version. >> >> When reviewing the history of xen-compat.h, it appeared that the version was >> bumped >> for each incompatible change. Considering there are 8 bits of sub-minor >> space, why >> wouldn't it be bumped? It allows an integrator of new headers to review all >> change sets >> associated with this one header file to understand the work required for an >> import. > > Then be it that way if it is to Keir's liking. Yep it's fine by me. -- Keir