From: Philippe Proulx <eeppeliteloop@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/7] lttng-tools: bump to version 2.6.0
Date: Fri, 6 Mar 2015 12:35:52 -0500 [thread overview]
Message-ID: <1425663357-22541-3-git-send-email-eeppeliteloop@gmail.com> (raw)
In-Reply-To: <1425663357-22541-1-git-send-email-eeppeliteloop@gmail.com>
Signed-off-by: Philippe Proulx <eeppeliteloop@gmail.com>
---
package/lttng-tools/Config.in | 2 +-
package/lttng-tools/lttng-tools.hash | 2 +-
package/lttng-tools/lttng-tools.mk | 2 +-
3 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/package/lttng-tools/Config.in b/package/lttng-tools/Config.in
index ea969a5..a960b21 100644
--- a/package/lttng-tools/Config.in
+++ b/package/lttng-tools/Config.in
@@ -13,7 +13,7 @@ config BR2_PACKAGE_LTTNG_TOOLS
depends on BR2_USE_WCHAR # util-linux
depends on BR2_TOOLCHAIN_HAS_THREADS
help
- Userspace utilities for the LTTng 2.0 tracing
+ Userspace utilities for the LTTng 2.x tracing
infrastructure.
Those utilities are required on the target system to start
diff --git a/package/lttng-tools/lttng-tools.hash b/package/lttng-tools/lttng-tools.hash
index fc2640e..a356911 100644
--- a/package/lttng-tools/lttng-tools.hash
+++ b/package/lttng-tools/lttng-tools.hash
@@ -1,2 +1,2 @@
# Locally generated
-sha256 1f52d342fb5b56a6675748f0b8e8557ec7c4e90732c3d8f5732bd10b920b233d lttng-tools-2.5.2.tar.bz2
+sha256 128166445126d76da7d9f42a56dec12716732a1ed697a6cfdf40c9e135384f32 lttng-tools-2.6.0.tar.bz2
diff --git a/package/lttng-tools/lttng-tools.mk b/package/lttng-tools/lttng-tools.mk
index 44b6880..e218a95 100644
--- a/package/lttng-tools/lttng-tools.mk
+++ b/package/lttng-tools/lttng-tools.mk
@@ -4,7 +4,7 @@
#
################################################################################
-LTTNG_TOOLS_VERSION = 2.5.2
+LTTNG_TOOLS_VERSION = 2.6.0
LTTNG_TOOLS_SITE = http://lttng.org/files/lttng-tools
LTTNG_TOOLS_SOURCE = lttng-tools-$(LTTNG_TOOLS_VERSION).tar.bz2
LTTNG_TOOLS_LICENSE = GPLv2+; LGPLv2.1+ for include/lttng/* and src/lib/lttng-ctl/*
--
2.2.1
next prev parent reply other threads:[~2015-03-06 17:35 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-06 17:35 [Buildroot] [PATCH 0/7] General LTTng packages maintenance Philippe Proulx
2015-03-06 17:35 ` [Buildroot] [PATCH 1/7] liburcu: bump to version 0.8.6 Philippe Proulx
2015-03-06 22:21 ` Thomas Petazzoni
2015-03-06 17:35 ` Philippe Proulx [this message]
2015-03-06 22:21 ` [Buildroot] [PATCH 2/7] lttng-tools: bump to version 2.6.0 Thomas Petazzoni
2015-03-06 17:35 ` [Buildroot] [PATCH 3/7] lttng-libust: " Philippe Proulx
2015-03-06 22:24 ` Thomas Petazzoni
2015-03-07 0:33 ` Philippe Proulx
2015-03-06 17:35 ` [Buildroot] [PATCH 4/7] lttng-modules: " Philippe Proulx
2015-03-06 22:28 ` Thomas Petazzoni
2015-03-07 0:35 ` Philippe Proulx
2015-03-06 17:35 ` [Buildroot] [PATCH 5/7] lttng-babeltrace: update Config.in's help Philippe Proulx
2015-03-06 22:30 ` Thomas Petazzoni
2015-03-06 17:35 ` [Buildroot] [PATCH 6/7] lttng-libust: rename package to lttng-ust Philippe Proulx
2015-03-06 17:35 ` [Buildroot] [PATCH 7/7] lttng-babeltrace: rename package to babeltrace Philippe Proulx
2015-03-06 22:32 ` [Buildroot] [PATCH 0/7] General LTTng packages maintenance Thomas Petazzoni
2015-03-07 1:02 ` Arnout Vandecappelle
2015-03-07 7:59 ` Thomas Petazzoni
2015-03-07 20:50 ` Philippe Proulx
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=1425663357-22541-3-git-send-email-eeppeliteloop@gmail.com \
--to=eeppeliteloop@gmail.com \
--cc=buildroot@busybox.net \
/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