From: Martin Jansa <martin.jansa@gmail.com>
To: Samuli Piippo <samuli.piippo@gmail.com>
Cc: openembedded-devel <openembedded-devel@lists.openembedded.org>
Subject: Re: [meta-qt5][PATCH] qt5: Update to Qt 5.11.0
Date: Wed, 20 Jun 2018 14:19:27 +0200 [thread overview]
Message-ID: <20180620121927.GB3257@jama> (raw)
In-Reply-To: <CABXoSoU8YpM1XNNDW7r=9vjhNtuJGwsT9Z+BCHvv7pBA=dy7wg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 479 bytes --]
On Wed, Jun 20, 2018 at 02:57:39PM +0300, Samuli Piippo wrote:
> On 20 June 2018 at 14:29, Martin Jansa <martin.jansa@gmail.com> wrote:
> > 3) we cannot use nobranch=1, because that breaks AUTOREV
>
> How does it break AUTOREV?
> We are using nobranch=1 when testing non-released Qt versions and
> haven't seen issues with it.
And are you using AUTOREV? How is it supposed to know which branch to
track?
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 201 bytes --]
next prev parent reply other threads:[~2018-06-20 12:19 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-29 9:25 [meta-qt5][PATCH] qt5: Update to Qt 5.11.0 Samuli Piippo
2018-06-06 20:05 ` Martin Jansa
2018-06-08 4:21 ` Samuli Piippo
2018-06-15 5:44 ` Samuli Piippo
2018-06-20 10:07 ` Daniel Mack
2018-06-20 10:36 ` Martin Jansa
2018-06-20 10:50 ` Daniel Mack
2018-06-20 11:29 ` Martin Jansa
2018-06-20 11:57 ` Samuli Piippo
2018-06-20 12:19 ` Martin Jansa [this message]
2018-06-20 13:38 ` Samuli Piippo
2018-06-21 5:14 ` Samuli Piippo
2018-06-21 9:03 ` Martin Jansa
2018-06-21 9:55 ` Samuli Piippo
2018-06-20 13:52 ` Daniel Mack
2018-06-20 18:06 ` Martin Jansa
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=20180620121927.GB3257@jama \
--to=martin.jansa@gmail.com \
--cc=openembedded-devel@lists.openembedded.org \
--cc=samuli.piippo@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox