Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/collectd: bump version to 5.5.1
Date: Wed, 27 Jan 2016 21:36:15 +0100	[thread overview]
Message-ID: <20160127213615.0a5a96dd@free-electrons.com> (raw)
In-Reply-To: <1453924918-27836-1-git-send-email-bernd.kuhls@t-online.de>

Dear Bernd Kuhls,

On Wed, 27 Jan 2016 21:01:58 +0100, Bernd Kuhls wrote:
> Removed COLLECTD_AUTORECONF=yes because our patches applied were applied
> upstream:
> http://git.verplant.org/?p=collectd.git;a=commitdiff;h=780e6a76021a240e95007a04b723d827120afa95
> http://git.verplant.org/?p=collectd.git;a=commitdiff;h=3e3848349b753d78a0b1d19648fb394866856bda
> 
> Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de>
> ---
>  ...libavltree-libcommon-libheap-dependencies.patch | 21 ----------------
>  package/collectd/0002-ipc-enable-gnu-source.patch  | 28 ----------------------
>  package/collectd/collectd.hash                     |  4 ++--
>  package/collectd/collectd.mk                       |  4 +---
>  4 files changed, 3 insertions(+), 54 deletions(-)
>  delete mode 100644 package/collectd/0001-build-add-libavltree-libcommon-libheap-dependencies.patch
>  delete mode 100644 package/collectd/0002-ipc-enable-gnu-source.patch

Aaah, this one, I like! I like when we can drop patches because they
have been upstreamed, and when in addition to this we can drop a
<pkg>_AUTORECONF = YES assignment.

I want more of such patches ! :-)

Obviously applied, thanks!

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

      reply	other threads:[~2016-01-27 20:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-27 20:01 [Buildroot] [PATCH 1/1] package/collectd: bump version to 5.5.1 Bernd Kuhls
2016-01-27 20:36 ` 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=20160127213615.0a5a96dd@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