From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Otavio Salvador <otavio.salvador@ossystems.com.br>,
"Burton, Ross" <ross.burton@intel.com>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 13/13] weston: Upgrade 1.9.0 -> 1.10.0
Date: Tue, 17 May 2016 21:24:25 +0100 [thread overview]
Message-ID: <1463516665.4578.24.camel@linuxfoundation.org> (raw)
In-Reply-To: <CAP9ODKqSG31qa3Au7g04DMjQmn+B4Xzz2Rtm2Ym0xYs55Mc-PA@mail.gmail.com>
On Tue, 2016-05-17 at 11:00 -0300, Otavio Salvador wrote:
> On Tue, May 17, 2016 at 5:38 AM, Burton, Ross <ross.burton@intel.com>
> wrote:
> >
> > On 17 May 2016 at 08:31, Jussi Kukkonen <jussi.kukkonen@intel.com>
> > wrote:
> > >
> > > There's not much to work on as far as I can tell: 1.11 should be
> > > a
> > > simple upgrade with trivial patch changes.
> > > As I said, I'm totally fine with waiting a couple of weeks until
> > > 1.11.
> > > On the other hand I haven't seen any reasons to start packaging a
> > > pre-release -- why this one if we normally don't do it?
> >
> >
> > Agreed, if we want an upgrade now then 1.10 is good, otherwise wait
> > for
> > 1.11. There's no urgent need for a prerelease is there?
>
> So please do 1.10 now, as the XWayland rework was done basing on that
> ... we can handle 1.11 upgrade once it happens.
I fixed up the selftest failure the original patch as proposed caused
and have merged that. Anything further can be based on that...
Cheers,
Richard
next prev parent reply other threads:[~2016-05-17 20:24 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-12 7:20 [PATCH 00/13] Upgrades around graphics stack Jussi Kukkonen
2016-05-12 7:20 ` [PATCH 01/13] xserver-xorg: Upgrade 1.18.0 -> 1.18.3 Jussi Kukkonen
2016-05-12 7:20 ` [PATCH 02/13] xrandr: Upgrade to 1.5.0 Jussi Kukkonen
2016-05-12 7:20 ` [PATCH 03/13] xkeyboard-config: Upgrade to 2.17 Jussi Kukkonen
2016-05-12 7:20 ` [PATCH 04/13] libinput: Upgrade 1.1.4 -> 1.3.0 Jussi Kukkonen
2016-05-12 7:20 ` [PATCH 05/13] xf86-input-evdev: Upgrade 2.10.1 -> 2.10.2 Jussi Kukkonen
2016-05-12 7:20 ` [PATCH 06/13] videoproto: Upgrade 2.3.2 -> 2.3.3 Jussi Kukkonen
2016-05-12 7:20 ` [PATCH 07/13] libxkbcommon: Upgrade 0.5.0 -> 0.6.1 Jussi Kukkonen
2016-05-12 7:20 ` [PATCH 08/13] libdrm: Upgrade 2.4.67 -> 2.4.68 Jussi Kukkonen
2016-05-12 7:20 ` [PATCH 09/13] mesa: Upgrade 11.1.1 -> 11.2.2 Jussi Kukkonen
2016-05-12 7:20 ` [PATCH 10/13] pixman: Upgrade 0.32.8 -> 0.34.0 Jussi Kukkonen
2016-05-12 7:20 ` [PATCH 11/13] wayland: Upgrade 1.9.0 -> 1.10.0 Jussi Kukkonen
2016-05-12 7:20 ` [PATCH 12/13] wayland-protocols: Add recipe Jussi Kukkonen
2016-05-13 9:15 ` Burton, Ross
2016-05-13 11:04 ` Jussi Kukkonen
2016-05-12 7:20 ` [PATCH 13/13] weston: Upgrade 1.9.0 -> 1.10.0 Jussi Kukkonen
2016-05-13 20:15 ` Otavio Salvador
2016-05-16 8:18 ` Jussi Kukkonen
2016-05-16 10:43 ` Otavio Salvador
2016-05-16 15:50 ` Khem Raj
2016-05-16 16:22 ` Otavio Salvador
2016-05-17 7:31 ` Jussi Kukkonen
2016-05-17 8:38 ` Burton, Ross
2016-05-17 14:00 ` Otavio Salvador
2016-05-17 20:24 ` Richard Purdie [this message]
2016-05-18 7:17 ` Jussi Kukkonen
2016-07-13 6:49 ` Khem Raj
2016-07-13 7:31 ` Jussi Kukkonen
2016-05-26 17:23 ` Martin Jansa
2016-05-26 19:13 ` Burton, Ross
2016-05-26 19:14 ` Burton, Ross
2016-06-01 12:49 ` [PATCH] libsdl2: Fix build with wayland 1.10 Martin Jansa
2016-05-12 7:57 ` [PATCH 00/13] Upgrades around graphics stack Jussi Kukkonen
-- strict thread matches above, loose matches on Subject: below --
2016-05-16 13:22 [PATCH 01/13] glib-2.0: Upgrade 2.46.2 -> 2.48.1 Jussi Kukkonen
2016-05-16 13:22 ` [PATCH 00/13] wayland V2 and misc upgrades Jussi Kukkonen
2016-05-16 13:22 ` [PATCH 13/13] weston: Upgrade 1.9.0 -> 1.10.0 Jussi Kukkonen
2016-05-16 15:37 ` Denys Dmytriyenko
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=1463516665.4578.24.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=otavio.salvador@ossystems.com.br \
--cc=ross.burton@intel.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.