From: "Jérémie Galarneau" <jeremie.galarneau@efficios.com>
To: lttng-dev@lists.lttng.org, diamon-discuss@lists.linuxfoundation.org
Subject: [diamon-discuss] [RELEASE] Babeltrace 2.0.1 - Amqui
Date: Tue, 4 Feb 2020 16:48:05 -0500 [thread overview]
Message-ID: <20200204214805.GA106763@gmail.com> (raw)
Hi everyone!
Today we're releasing the first patch-level release of Babeltrace 2.0
"Amqui".
What's new since Babeltrace 2.0.0?
==================================
This release contains minor bug fixes which are mainly
related to packaging and documentation issues.
Of note for packagers, we have changed the autoconf package name to
`babeltrace2`. This fixes co-installation problems with Babeltrace
1.x, but also changes the naming scheme of the official tarball.
The official tarballs of Babeltrace 2 are now named
`babeltrace2-$VERSION.tar.bz2`. We have added a symlink to reflect
this naming scheme to the prior Babeltrace 2.0.0 release.
The full change log follows.
2020-02-04 Babeltrace 2.0.1
* fix: Remove empty python bindings documentation
* README: Babeltrace 2 was released in 2020
* fix: set autoconf package name to babeltrace2
* Typo: occured -> occurred
* .gitignore: Add missing bt2/native_bt.d
* fix: build failure on ppc64el with '-Werror=format-overflow='
* Silence -Wnull-dereference warning in generated CTF parser code
* plugin-so.c: add comment about why we're not using a GLib linked list
* doc: graph.h: do not link to `man7.org` for `babeltrace(1)`
* fix: common/list.h is LGPL-2.1
* fix: build Python bindings with GCC10
* fix: use correct function to print 'enum bt_ctf_scope'
* Update working version to Babeltrace 2.0.1
Important links
===============
Babeltrace 2.0.1 tarball:
https://www.efficios.com/files/babeltrace/babeltrace2-2.0.1.tar.bz2
Babeltrace website:
https://babeltrace.org
Mailing list (for support and development):
`lttng-dev at lists.lttng.org`
IRC channel:
`#lttng` on `irc.oftc.net`
Git repository:
https://bugs.lttng.org/projects/babeltrace
GitHub project:
https://github.com/efficios/babeltrace
Continuous integration:
https://ci.lttng.org/view/Babeltrace/
Code review:
https://review.lttng.org/q/project:babeltrace
WARNING: multiple messages have this Message-ID (diff)
From: "Jérémie Galarneau" <jeremie.galarneau@efficios.com>
To: lttng-dev@lists.lttng.org, diamon-discuss@lists.linuxfoundation.org
Subject: [RELEASE] Babeltrace 2.0.1 - Amqui
Date: Tue, 4 Feb 2020 16:48:05 -0500 [thread overview]
Message-ID: <20200204214805.GA106763@gmail.com> (raw)
Hi everyone!
Today we're releasing the first patch-level release of Babeltrace 2.0
"Amqui".
What's new since Babeltrace 2.0.0?
==================================
This release contains minor bug fixes which are mainly
related to packaging and documentation issues.
Of note for packagers, we have changed the autoconf package name to
`babeltrace2`. This fixes co-installation problems with Babeltrace
1.x, but also changes the naming scheme of the official tarball.
The official tarballs of Babeltrace 2 are now named
`babeltrace2-$VERSION.tar.bz2`. We have added a symlink to reflect
this naming scheme to the prior Babeltrace 2.0.0 release.
The full change log follows.
2020-02-04 Babeltrace 2.0.1
* fix: Remove empty python bindings documentation
* README: Babeltrace 2 was released in 2020
* fix: set autoconf package name to babeltrace2
* Typo: occured -> occurred
* .gitignore: Add missing bt2/native_bt.d
* fix: build failure on ppc64el with '-Werror=format-overflow='
* Silence -Wnull-dereference warning in generated CTF parser code
* plugin-so.c: add comment about why we're not using a GLib linked list
* doc: graph.h: do not link to `man7.org` for `babeltrace(1)`
* fix: common/list.h is LGPL-2.1
* fix: build Python bindings with GCC10
* fix: use correct function to print 'enum bt_ctf_scope'
* Update working version to Babeltrace 2.0.1
Important links
===============
Babeltrace 2.0.1 tarball:
https://www.efficios.com/files/babeltrace/babeltrace2-2.0.1.tar.bz2
Babeltrace website:
https://babeltrace.org
Mailing list (for support and development):
`lttng-dev at lists.lttng.org`
IRC channel:
`#lttng` on `irc.oftc.net`
Git repository:
https://bugs.lttng.org/projects/babeltrace
GitHub project:
https://github.com/efficios/babeltrace
Continuous integration:
https://ci.lttng.org/view/Babeltrace/
Code review:
https://review.lttng.org/q/project:babeltrace
next reply other threads:[~2020-02-04 21:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-04 21:48 Jérémie Galarneau [this message]
2020-02-04 21:48 ` [RELEASE] Babeltrace 2.0.1 - Amqui Jérémie Galarneau
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=20200204214805.GA106763@gmail.com \
--to=jeremie.galarneau@efficios.com \
--cc=diamon-discuss@lists.linuxfoundation.org \
--cc=lttng-dev@lists.lttng.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.