On Mon, Jan 27, 2020 at 09:53:11PM +0100, Roland Knall wrote:
> Well it took me a while to read through all the comments.
Indeed, some highlights:
* A Qt community contributor suggests potential adverse effects for the
Qt Company such as forking and less contributions.
On Jan 27, 2020, at 12:53 PM, Roland Knall wrote:
> Finally, I would not call it a day yet. Qt has become a very strategic
> project for a lot of people. I could imagine, that the outcry over this
> decision will be as big as the one 2015 over the first attempt to close down
> the installer.
Well it took me a while to read through all the comments.
First of all, I understand their - Qt's - reasoning. It makes sense from a
business side of things, and they are getting rather big. Developing that
framework is not the easiest task and they need money (sounds too
familiar). This sucks,
On Mon, 27 Jan 2020 at 20:06, Gerald Combs wrote:
> The Qt Company recently announced upcoming changes in the distribution of
> their official binaries:
>
> https://www.qt.io/blog/qt-offering-changes-2020
>
> https://lists.qt-project.org/pipermail/development/2020-January/thread.html#38316
>
>
The Qt Company recently announced upcoming changes in the distribution of their
official binaries:
https://www.qt.io/blog/qt-offering-changes-2020
https://lists.qt-project.org/pipermail/development/2020-January/thread.html#38316
Two of the changes adversely affect how we develop and build
On 1/26/2020 7:15 AM, Patrick Klos wrote:
On 1/26/2020 3:46 AM, Erwin Rol wrote:
Hey all,
I was wondering if there is a remote capture "protocol" that works on
Mac, Windows, and Linux?
The idea I have is to use a small (and cheap) microcontroller like a
STM32F407 that can capture a fieldbus
Hi,
I’ve uploaded https://code.wireshark.org/review/35959, which is a patch on
master, I see the that code has changed a bit since 2.4.5.
/Anders
From: Wireshark-dev on behalf of Dario
Lombardo
Reply to: Developer support list for Wireshark
Date: Sunday, 26 January 2020 at 09.34
To:
