From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-qt5][PATCH 7/7] qt5: upgrade git recipes to 5.4-alpha1
Date: Sat, 4 Oct 2014 17:49:52 +0200 [thread overview]
Message-ID: <20141004154952.GP25706@jama> (raw)
In-Reply-To: <1412389558-13237-7-git-send-email-Martin.Jansa@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 797 bytes --]
On Sat, Oct 04, 2014 at 04:25:58AM +0200, Martin Jansa wrote:
> * introduce 2nd set of qtwayland and qtwebengine recipes, because newer
> revision isn't compatible with 5.3.2 release
I plan to merge all these changes into master before branching dizzy, do
you have some good reason for me to wait after branching?
Pros:
* It's already tested with dizzy.
* I don't think that anybody would require 5.3 from git, now when it
receives only relatively few changes.
* Possibility to try 5.4 with dizzy branch (but useful only for very
short time)
Cons:
* All serious 5.4 users will use meta-qt5 from some later commit in master
branch (e.g. after 5.4.0 is released), using stable "release" branch
for metadata and alpha release of qt doesn't make much sense.
Regards,
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 188 bytes --]
prev parent reply other threads:[~2014-10-04 15:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-04 2:25 [meta-qt5][PATCH 1/7] qt5: Add Qt 5.3.2 packages Martin Jansa
2014-10-04 2:25 ` [meta-qt5][PATCH 2/7] qtwebengine: update repository location Martin Jansa
2014-10-04 2:25 ` [meta-qt5][PATCH 3/7] qtbwebengine: fix build for qemux86-64 Martin Jansa
2014-10-04 2:25 ` [meta-qt5][PATCH 4/7] qt*: refresh the patches Martin Jansa
2014-10-04 2:25 ` [meta-qt5][PATCH 5/7] qtbase: Drop dont-process configure option Martin Jansa
2014-10-04 2:25 ` [meta-qt5][PATCH 6/7] qtwayland-native: remove qtwaylandscanner symlink Martin Jansa
2014-10-04 2:25 ` [meta-qt5][PATCH 7/7] qt5: upgrade git recipes to 5.4-alpha1 Martin Jansa
2014-10-04 15:49 ` Martin Jansa [this message]
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=20141004154952.GP25706@jama \
--to=martin.jansa@gmail.com \
--cc=openembedded-devel@lists.openembedded.org \
/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