[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] [PATCH 0 of 4 v2] blkif.h: Document protocol and existing extensions

  • To: Jan Beulich <JBeulich@xxxxxxxx>, "Justin T. Gibbs" <justing@xxxxxxxxxxxxxxxx>
  • From: Keir Fraser <keir.xen@xxxxxxxxx>
  • Date: Wed, 15 Feb 2012 17:11:13 +0000
  • Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Wed, 15 Feb 2012 17:11:44 +0000
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AczsBNHAj8zKgKX5QkuWJdEJI7L8QA==
  • Thread-topic: [Xen-devel] [PATCH 0 of 4 v2] blkif.h: Document protocol and existing extensions

On 15/02/2012 13:16, "Jan Beulich" <JBeulich@xxxxxxxx> 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

Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.