From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH next 3/4] lttng-babeltrace: bump version to 1.5.0
Date: Sat, 3 Dec 2016 14:35:04 +0100 [thread overview]
Message-ID: <20161203143504.5a31e6ab@free-electrons.com> (raw)
In-Reply-To: <20161130170445.55222-3-Vincent.Riera@imgtec.com>
Hello,
On Wed, 30 Nov 2016 17:04:44 +0000, Vicente Olivert Riera wrote:
> Drop sha256 hash. The combination of md5 and sha1 hashes is enough.
>
> Release notes:
> https://lists.lttng.org/pipermail/lttng-dev/2016-November/026762.html
>
> Signed-off-by: Vicente Olivert Riera <Vincent.Riera@imgtec.com>
> ---
> package/lttng-babeltrace/lttng-babeltrace.hash | 9 +++------
> package/lttng-babeltrace/lttng-babeltrace.mk | 2 +-
> 2 files changed, 4 insertions(+), 7 deletions(-)
This was apparently not tested at all: one of the patches fails to
apply, see
http://autobuild.buildroot.net/results/98a/98a42516fa7e2c79e5529d1b5a8d44fcd60934c7/build-end.log.
Could you have a look?
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-12-03 13:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-30 17:04 [Buildroot] [PATCH next 1/4] lttng-tools: bump version to 2.9.0 Vicente Olivert Riera
2016-11-30 17:04 ` [Buildroot] [PATCH next 2/4] lttng-modules: " Vicente Olivert Riera
2016-11-30 17:04 ` [Buildroot] [PATCH next 3/4] lttng-babeltrace: bump version to 1.5.0 Vicente Olivert Riera
2016-12-03 13:35 ` Thomas Petazzoni [this message]
2016-11-30 17:04 ` [Buildroot] [PATCH next 4/4] lttng-libust: bump version to 2.9.0 Vicente Olivert Riera
2016-11-30 17:53 ` [Buildroot] [PATCH next 1/4] lttng-tools: " Baruch Siach
2016-11-30 21:03 ` Thomas Petazzoni
2016-11-30 21:09 ` Thomas Petazzoni
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=20161203143504.5a31e6ab@free-electrons.com \
--to=thomas.petazzoni@free-electrons.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