From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] libepoxy: bump to version 1.4.3
Date: Mon, 14 Aug 2017 21:31:13 +0200 [thread overview]
Message-ID: <20170814213113.6187b327@windsurf> (raw)
In-Reply-To: <20170814172320.16984-1-aperez@igalia.com>
Hello,
On Mon, 14 Aug 2017 20:23:20 +0300, Adrian Perez de Castro wrote:
> Among other small fixes, the new version fixes crashes when running in
> X11 without GLX (i.e. using EGL). Additionally, the changes from patch
> "0002-Make-EGL-support-optional.patch" were committed upstream, and the
> file can be dropped.
>
> Signed-off-by: Adrian Perez de Castro <aperez@igalia.com>
Since we're post -rc2 comes the question: do we want to apply this in
master (i.e to be part of the 2017.08 release) or in next.
If it fixes a crash, we probably want it in master. But version bumps
are a bit frowned upon. How much differences are there between 1.4.1
and 1.4.3 ? Are they significant ? If they are significant, is it
possible to backport just the one patch that fixes the crash ?
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-08-14 19:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-14 17:23 [Buildroot] [PATCH 1/1] libepoxy: bump to version 1.4.3 Adrian Perez de Castro
2017-08-14 19:31 ` Thomas Petazzoni [this message]
2017-08-14 20:06 ` Adrian Perez de Castro
2017-08-14 20:15 ` Thomas Petazzoni
2017-08-16 13:49 ` Adrian Perez de Castro
2017-08-16 14:44 ` Thomas Petazzoni
2017-08-21 21:36 ` 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=20170814213113.6187b327@windsurf \
--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