From: Doug Goldstein <cardoe@cardoe.com>
To: Ponomarenko Andrey <andrewponomarenko@yandex.ru>,
xen-users@lists.xen.org
Cc: xen-devel@lists.xen.org
Subject: Re: Binary compatibility report for Xen base libraries
Date: Fri, 24 Jun 2016 09:42:07 -0500 [thread overview]
Message-ID: <5571cc13-6b01-307d-501f-35e063b53278@cardoe.com> (raw)
In-Reply-To: <97921466778072@web1h.yandex.ru>
[-- Attachment #1.1.1: Type: text/plain, Size: 891 bytes --]
On 6/24/16 9:21 AM, Ponomarenko Andrey wrote:
> Hello,
>
> I maintain a new project for backward compatibility analysis of the Linux ABIs. The report for Xen base libraries has been recently added to the project: http://abi-laboratory.pro/tracker/timeline/xen/
>
> The report is generated daily with the help of the abi-compliance-checker, abi-dumper and abi-tracker tools: https://github.com/lvc/abi-tracker
>
> Hope this will help users, maintainers and developers to maintain backward compatibility.
>
> Thank you.
>
Outstanding! I had mentioned your tools in the #xen-devel channel. And I
had talked about utilizing them as part of the Travis build process with
the goal of making this data available. Thank you for doing this.
Do you have any advice for us if it would be positive to do some sort of
check on a per-commit basis or not?
--
Doug Goldstein
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 959 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-06-24 14:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-24 14:21 Binary compatibility report for Xen base libraries Ponomarenko Andrey
2016-06-24 14:42 ` Doug Goldstein [this message]
2016-06-27 13:49 ` [Xen-users] " Ponomarenko Andrey
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=5571cc13-6b01-307d-501f-35e063b53278@cardoe.com \
--to=cardoe@cardoe.com \
--cc=andrewponomarenko@yandex.ru \
--cc=xen-devel@lists.xen.org \
--cc=xen-users@lists.xen.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 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).