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] x11vnc: update to 0.9.14
Date: Wed, 26 Apr 2017 10:03:20 +0200	[thread overview]
Message-ID: <20170426100320.00702ce9@free-electrons.com> (raw)
In-Reply-To: <e8750710-f475-fe87-79a4-edd6f655d5a0@mind.be>

Hello,

On Mon, 24 Apr 2017 21:47:58 +0200, Arnout Vandecappelle wrote:

>  Is there a reason why you need this bump?

Well, do we need a reason to bump a package, other than "upstream has a
new release, possibly with new features/bug fixes" ? Tons of version
bumps we merged are not motivated by a specific reason, other than
making sure Buildroot uses recent versions of the different components.

Best regards,

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

  parent reply	other threads:[~2017-04-26  8:03 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-24 12:22 [Buildroot] [PATCH] x11vnc: update to 0.9.14 Martin Kepplinger
2017-04-24 12:27 ` Martin Kepplinger
2017-04-24 12:55   ` Vicente Olivert Riera
2017-04-24 13:26     ` Martin Kepplinger
2017-04-24 19:47       ` Arnout Vandecappelle
2017-04-25  7:23         ` Martin Kepplinger
2017-04-26  8:03         ` Thomas Petazzoni [this message]
2017-04-26 12:37           ` [Buildroot] [PATCH v2] " Martin Kepplinger
2017-04-28  7:02             ` Martin Kepplinger
2017-04-28 20:23             ` Arnout Vandecappelle
2017-04-29 13:00               ` [Buildroot] [PATCH v3] " Martin Kepplinger
2017-04-29 13:25                 ` Thomas Petazzoni
2017-04-28 20:17           ` [Buildroot] [PATCH] " Arnout Vandecappelle

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=20170426100320.00702ce9@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