From: "Jan Beulich" <JBeulich@novell.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: [PATCH] libxl: do not expose libxenctrl/libxenstore headers via libxl.h
Date: Thu, 07 Apr 2011 09:30:59 +0100 [thread overview]
Message-ID: <4D9D9263020000780003A58E@vpn.id2.novell.com> (raw)
In-Reply-To: <19868.35898.53337.358242@mariner.uk.xensource.com>
>>> On 06.04.11 at 17:52, Ian Jackson <Ian.Jackson@eu.citrix.com> wrote:
> Ian Campbell writes ("[Xen-devel] [PATCH] libxl: do not expose
> libxenctrl/libxenstore headers via libxl.h"):
>> libxl: do not expose libxenctrl/libxenstore headers via libxl.h
>>
>> This completely removes libxenstore from libxl users' view.
>>
>> xl still needs libxenctrl directly due to the direct use of the
>> xentoollog functionality but it is not exposed to the indirect linkage
>> anymore.
>
> Applied.
>
> Shame about the lack of API compatibility, but really the old was too
> awful.
Shouldn't API incompatible changes lead to immediate bumping of
the major version of the affected shared library?
Jan
next prev parent reply other threads:[~2011-04-07 8:30 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-06 15:19 [PATCH] libxl: do not expose libxenctrl/libxenstore headers via libxl.h Ian Campbell
2011-04-06 15:52 ` Ian Jackson
2011-04-07 8:30 ` Jan Beulich [this message]
2011-04-07 8:52 ` Ian Campbell
2011-04-07 9:32 ` Jan Beulich
2011-04-07 9:58 ` Ian Jackson
2011-04-07 10:23 ` Stefano Stabellini
2011-04-08 15:17 ` Ian Jackson
2011-04-13 4:07 ` Jim Fehlig
2011-04-13 10:06 ` libxl API changes for 4.2 (Was: Re: [PATCH] libxl: do not expose libxenctrl/libxenstore headers via libxl.h) Ian Campbell
2011-04-13 10:12 ` Christoph Egger
2011-04-13 11:00 ` Ian Campbell
2011-04-13 11:04 ` Ian Jackson
2011-04-13 11:03 ` Ian Jackson
2011-04-14 17:41 ` Jim Fehlig
2011-04-15 8:24 ` Ian Campbell
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=4D9D9263020000780003A58E@vpn.id2.novell.com \
--to=jbeulich@novell.com \
--cc=Ian.Jackson@eu.citrix.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).