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 v4 1/2] libgtk3: bump to version 3.18.9
Date: Tue, 22 Mar 2016 10:03:44 +0100	[thread overview]
Message-ID: <20160322100344.3d45d248@free-electrons.com> (raw)
In-Reply-To: <1458561948-13971-2-git-send-email-gustavo@zacarias.com.ar>

Hello,

On Mon, 21 Mar 2016 09:05:47 -0300, Gustavo Zacarias wrote:
> Mark the wayland backend as good again since the bump and consequent
> protocol version match fixes it.
> 
> Drop upstream 0004-Fix-undefined-reference-to-get_xkb.patch
> 
> Drop unnecessary 0005-do-not-build-extract-strings.patch
> (extract-strings doesn't exist any more).
> 
> Signed-off-by: Gustavo Zacarias <gustavo@zacarias.com.ar>
> ---
>  .../0004-Fix-undefined-reference-to-get_xkb.patch  | 33 --------
>  .../0005-do-not-build-extract-strings.patch        | 47 ------------
>  package/libgtk3/Config.in                          | 88 +++++++++++++---------
>  package/libgtk3/libgtk3.hash                       |  4 +-
>  package/libgtk3/libgtk3.mk                         | 15 +---
>  5 files changed, 57 insertions(+), 130 deletions(-)
>  delete mode 100644 package/libgtk3/0004-Fix-undefined-reference-to-get_xkb.patch
>  delete mode 100644 package/libgtk3/0005-do-not-build-extract-strings.patch

Applied to master, thanks.

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

  reply	other threads:[~2016-03-22  9:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-21 12:05 [Buildroot] [PATCH v4 0/2] gtk3 bump Gustavo Zacarias
2016-03-21 12:05 ` [Buildroot] [PATCH v4 1/2] libgtk3: bump to version 3.18.9 Gustavo Zacarias
2016-03-22  9:03   ` Thomas Petazzoni [this message]
2016-03-21 12:05 ` [Buildroot] [PATCH v4 2/2] gtkmm3: bump to version 3.18.0 Gustavo Zacarias
2016-03-22  9:04   ` 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=20160322100344.3d45d248@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