Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/lttng-babeltrace: bump to version 1.5.7
Date: Sat, 7 Sep 2019 14:47:48 +0200	[thread overview]
Message-ID: <20190907144748.5f96199e@windsurf> (raw)
In-Reply-To: <20190905171020.3705-1-fontaine.fabrice@gmail.com>

Hello Fabrice,

On Thu,  5 Sep 2019 19:10:20 +0200
Fabrice Fontaine <fontaine.fabrice@gmail.com> wrote:

> - Remove second patch (already in version)
> - Add hash for license files
> 
> Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
> ---
>  ...x_lib_elfutils.m4-add-cache-variable.patch | 77 -------------------
>  .../lttng-babeltrace/lttng-babeltrace.hash    | 10 ++-
>  package/lttng-babeltrace/lttng-babeltrace.mk  |  4 +-
>  3 files changed, 9 insertions(+), 82 deletions(-)
>  delete mode 100644 package/lttng-babeltrace/0002-m4-ax_lib_elfutils.m4-add-cache-variable.patch

Applied to master, thanks. When you're doing version bumps, it would be
nice if you could check that the release-monitoring.org information for
that package is correct, and that Buildroot finds it properly through
pkg-stats (see also http://autobuild.buildroot.net/stats/). In this
case, it was just a matter of adding a mapping lttng-babeltrace ->
babeltrace on release-monitoring.org for the Buildroot distribution.

Thanks,

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

      reply	other threads:[~2019-09-07 12:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-05 17:10 [Buildroot] [PATCH 1/1] package/lttng-babeltrace: bump to version 1.5.7 Fabrice Fontaine
2019-09-07 12:47 ` Thomas Petazzoni [this message]

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=20190907144748.5f96199e@windsurf \
    --to=thomas.petazzoni@bootlin.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