From: "Jan Beulich" <JBeulich@suse.com>
To: "Roger Pau Monné" <roger.pau@citrix.com>
Cc: Stefano Stabellini <sstabellini@kernel.org>,
WeiLiu <wei.liu2@citrix.com>,
George Dunlap <George.Dunlap@eu.citrix.com>,
Andrew Cooper <andrew.cooper3@citrix.com>,
Ian Jackson <ian.jackson@eu.citrix.com>, Tim Deegan <tim@xen.org>,
xen-devel@lists.xenproject.org
Subject: Re: when to bump library versions (was: <blank>)
Date: Thu, 19 May 2016 09:01:28 -0600 [thread overview]
Message-ID: <573DF16802000078000ECFF5@prv-mh.provo.novell.com> (raw)
In-Reply-To: <20160519145336.ug3ysll2tzw4aupk@mac>
>>> On 19.05.16 at 16:53, <roger.pau@citrix.com> wrote:
> On Thu, May 19, 2016 at 08:44:59AM -0600, Jan Beulich wrote:
>> >>> On 19.05.16 at 16:34, <roger.pau@citrix.com> wrote:
>> > We could even have the
>> > library name versions be set based on XEN_VERSION and XEN_SUBVERSION, so
>> > that we don't need to go around the different library makefiles bumping the
>> > versions manually.
>>
>> But so far these two are intentionally private to the xen/ subtree.
>
> Maybe I'm missing something, but couldn't they be global to the whole tree?
> (Config.mk seems like a suitable place).
I think originally the idea was that the tool stack isn't really tied to
a specific hypervisor version. What it is tied to is an interface
version (of namely domctl and sysctl).
Jan
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-05-19 15:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-19 14:34 (no subject) Roger Pau Monné
2016-05-19 14:44 ` when to bump library versions (was: <blank>) Jan Beulich
2016-05-19 14:53 ` Roger Pau Monné
2016-05-19 15:01 ` Jan Beulich [this message]
2016-05-23 11:06 ` George Dunlap
2016-06-06 12:33 ` Wei Liu
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=573DF16802000078000ECFF5@prv-mh.provo.novell.com \
--to=jbeulich@suse.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=andrew.cooper3@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=roger.pau@citrix.com \
--cc=sstabellini@kernel.org \
--cc=tim@xen.org \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xenproject.org \
/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.