Hello,
Thanks to all for the answers.
Actually, we did not fix the problem. All we did - recompiled Qt w/
OpenSSL library to avoid the problem on Mac OS X. This helped.
Later, one of your programmers reported that he fixed the problem. But
we did not test it yet.
On 11/29/2016 5:00 PM,
On terça-feira, 29 de novembro de 2016 17:51:28 PST Jake Petroules wrote:
> See, this is why we need to make submissions on JIRA require signing the
> CLA. People simply don't want to go through the Gerrit hassle for drive-by
> contributions.
I'm not sure we should accept drive-by contributions
> > On terça-feira, 29 de novembro de 2016 09:00:21 PST Andy wrote:
> >> So I would suggest reporting the bug at https://bugreports.qt.io and
> >> attaching the fixes - then at least it exists somewhere and can be
> >> found/looked at/integrated by someone in the future.
> >
> > We cannot accept
> On Nov 29, 2016, at 9:27 AM, Thiago Macieira
> wrote:
>
> On terça-feira, 29 de novembro de 2016 09:00:21 PST Andy wrote:
>> So I would suggest reporting the bug at https://bugreports.qt.io and
>> attaching the fixes - then at least it exists somewhere and can be
On terça-feira, 29 de novembro de 2016 09:00:21 PST Andy wrote:
> So I would suggest reporting the bug at https://bugreports.qt.io and
> attaching the fixes - then at least it exists somewhere and can be
> found/looked at/integrated by someone in the future.
We cannot accept patches on the
On terça-feira, 29 de novembro de 2016 13:42:39 PST Alexander Dyagilev wrote:
> Hello,
>
> We use Qt under LGPL license.
>
> We have found some problem in it (bug working with HTTPS on limited
> connection speed) and fixed it. We have recompiled Qt then.
>
> What do we must to do next to obey
29.11.2016, 17:00, "Andy" :
> Back to Alexander's question...
>
> Should he choose to contribute the fixes back, signing up for, setting up,
> and working with gerritt is a PIA if you aren't using it frequently.
Doing initial setup is really easy if you follow instruction.
Back to Alexander's question...
Should he choose to contribute the fixes back, signing up for, setting up,
and working with gerritt is a PIA if you aren't using it frequently.
So I would suggest reporting the bug at https://bugreports.qt.io and
attaching the fixes - then at least it exists
29.11.2016, 14:57, "André Somers" :
> Op 29/11/2016 om 12:01 schreef Konstantin Tokarev:
>> 29.11.2016, 13:51, "André Somers" :
>>> Op 29/11/2016 om 11:42 schreef Alexander Dyagilev:
Hello,
We use Qt under LGPL license.
Op 29/11/2016 om 12:01 schreef Konstantin Tokarev:
29.11.2016, 13:51, "André Somers" :
Op 29/11/2016 om 11:42 schreef Alexander Dyagilev:
Hello,
We use Qt under LGPL license.
We have found some problem in it (bug working with HTTPS on limited
connection
29.11.2016, 13:45, "Jake Petroules" :
>> On Nov 29, 2016, at 2:42 AM, Alexander Dyagilev wrote:
>>
>> Hello,
>>
>> We use Qt under LGPL license.
>>
>> We have found some problem in it (bug working with HTTPS on limited
>> connection speed) and
29.11.2016, 13:51, "André Somers" :
> Op 29/11/2016 om 11:42 schreef Alexander Dyagilev:
>> Hello,
>>
>> We use Qt under LGPL license.
>>
>> We have found some problem in it (bug working with HTTPS on limited
>> connection speed) and fixed it. We have recompiled Qt
Op 29/11/2016 om 11:42 schreef Alexander Dyagilev:
Hello,
We use Qt under LGPL license.
We have found some problem in it (bug working with HTTPS on limited
connection speed) and fixed it. We have recompiled Qt then.
What do we must to do next to obey the license terms?
Publish the
> On 29 Nov 2016, at 10:45, Jake Petroules wrote:
>
>
>> On Nov 29, 2016, at 2:42 AM, Alexander Dyagilev wrote:
>>
>> Hello,
>>
>> We use Qt under LGPL license.
>>
>> We have found some problem in it (bug working with HTTPS on limited
>>
> On Nov 29, 2016, at 2:42 AM, Alexander Dyagilev wrote:
>
> Hello,
>
> We use Qt under LGPL license.
>
> We have found some problem in it (bug working with HTTPS on limited
> connection speed) and fixed it. We have recompiled Qt then.
>
> What do we must to do next to
15 matches
Mail list logo