From: Keir Fraser <keir.xen@gmail.com>
To: Jan Beulich <JBeulich@suse.com>,
"Justin T. Gibbs" <justing@spectralogic.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: [PATCH 0 of 4 v2] blkif.h: Document protocol and existing extensions
Date: Wed, 15 Feb 2012 17:11:13 +0000 [thread overview]
Message-ID: <CB6197B1.2B516%keir.xen@gmail.com> (raw)
In-Reply-To: <4F3BBE3F02000078000732C6@nat28.tlf.novell.com>
On 15/02/2012 13:16, "Jan Beulich" <JBeulich@suse.com> 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
prev parent reply other threads:[~2012-02-15 17:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-15 5:06 [PATCH 0 of 4 v2] blkif.h: Document protocol and existing extensions Justin T. Gibbs
2012-02-15 5:06 ` [PATCH 1 of 4 v2] blkif.h: Miscelaneous style fixes Justin T. Gibbs
2012-02-15 5:06 ` [PATCH 2 of 4 v2] blkif.h: Provide more complete documentation of the blkif interface Justin T. Gibbs
2012-02-15 5:06 ` [PATCH 3 of 4 v2] blkif.h: Document the RedHat and Citrix blkif multi-page ring extensions Justin T. Gibbs
2012-02-15 5:06 ` [PATCH 4 of 4 v2] blkif.h: Define and document the request number/size/segments extension Justin T. Gibbs
2012-02-16 8:42 ` Jan Beulich
2012-02-17 0:41 ` Justin T. Gibbs
2012-02-15 8:14 ` [PATCH 0 of 4 v2] blkif.h: Document protocol and existing extensions Jan Beulich
2012-02-15 13:03 ` Justin T. Gibbs
2012-02-15 13:16 ` Jan Beulich
2012-02-15 17:11 ` Keir Fraser [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=CB6197B1.2B516%keir.xen@gmail.com \
--to=keir.xen@gmail.com \
--cc=JBeulich@suse.com \
--cc=justing@spectralogic.com \
--cc=xen-devel@lists.xensource.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.