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 2/2] libnl: bump to version 3.2.29
Date: Fri, 10 Mar 2017 12:03:11 +0100	[thread overview]
Message-ID: <20170310120311.2517d6d3@free-electrons.com> (raw)
In-Reply-To: <061cbb4c-8b53-4f32-9d03-344b1ff0c009@zacarias.com.ar>

Hello,

On Fri, 10 Mar 2017 06:56:00 -0300, Gustavo Zacarias wrote:

> Did you try with older headers?
> Beacuse last time i tried 3.2.{28,29} weren't happy at least with 3.2.x 
> hence i refrained from bumping and carrying that dependency along a few 
> packages.

Thanks for this report. To avoid such bumps, it would be nice when you
realize a bump shouldn't be done for reason X, Y or Z, to send a patch
that adds a comment above the <pkg>_VERSION variable that indicates why
it shouldn't be bumped, or at least what the person doing the bump
should take care of :)

Thanks!

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

  parent reply	other threads:[~2017-03-10 11:03 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-10  8:54 [Buildroot] [PATCH 1/2] libnl: update homepage link Baruch Siach
2017-03-10  8:54 ` [Buildroot] [PATCH 2/2] libnl: bump to version 3.2.29 Baruch Siach
2017-03-10  9:56   ` Gustavo Zacarias
2017-03-10  9:57     ` Gustavo Zacarias
2017-03-10 10:34       ` Baruch Siach
2017-03-10 12:55         ` Baruch Siach
2017-03-10 13:05           ` Jeroen Roovers
2017-03-10 14:17             ` Baruch Siach
2017-03-10 11:03     ` Thomas Petazzoni [this message]
2017-03-10 20:41   ` Thomas Petazzoni
2017-03-10  9:29 ` [Buildroot] [PATCH 1/2] libnl: update homepage link 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=20170310120311.2517d6d3@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