| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
| |
As checked in was compiling with QDataStream(QByteArray *, int) and
that method is only available when compiling with qt3 support.
Reviewed-by: Julian de Bhal
|
| |
|
|
|
|
|
| |
seem fixable easily)
Merge-request: 594
Reviewed-by: Rohan McGovern <rohan.mcgovern@nokia.com>
|
| |
|
|
|
| |
used character operations whenever possible
better usage of QLatin1String
|
| |
|
|
|
|
|
|
|
| |
compilation breakage introduced in 6c1d7e57.
The fix in fc7a43cce did fix the failure, but created another one
because qhostinfo_win.cpp also had a copy of qt_sockaddr_in6
Reviewed-by: Jason McDonald
|
| |
|
|
|
| |
Task-number: 254333
Reviewed-by: Andy Shaw <qt-info@nokia.com>
|
| |
|
|
|
|
| |
Usually, "the the" is not proper English
Reviewed-By: Thiago Macieira
|
| |
|
|
|
| |
Task-number: 236925
Reviewed-by: Tor Arne Vestbø
|
| |
|
|
|
|
|
|
|
|
|
|
| |
If you write:
QNetworkProxy proxy;
proxy.setType(QNetworkProxy::HttpProxy);
Then now QNetworkProxy will set the capabilities to the default value
for the new proxy type. Previously, it wouldn't do that: default
values were set only for the type passed in the constructor.
Reviewed-by: Peter Hartmann
|
| |
|
|
|
|
| |
name resolution
Task-number: 252761
|
| |
|
|
| |
i.e., use "", not <> and thus rely on the include path
|
| |
|
|
|
|
|
|
| |
Before, we returned 0 for many interfaces because we picked up the IPv6
address regardless whether it was 0 or not.
Reviewed-by: Prasanth Ullattil <prasanth.ullattil@nokia.com>
Task-number: 249312
|
| |
|
|
|
|
|
| |
the task.
Task-number: 249423
Reviewed-by: TrustMe
|
| |
|
