diff options
| author | Janne Anttila <janne.anttila@digia.com> | 2009-08-11 06:53:49 (GMT) |
|---|---|---|
| committer | Janne Anttila <janne.anttila@digia.com> | 2009-08-11 06:53:49 (GMT) |
| commit | d1ce08936b4a6f4ce2b2e878287de76d47df0b8c (patch) | |
| tree | 6f846146babb655b5ad5239a79a767b9ea505c3a /mkspecs/win32-borland | |
| parent | aa11cdf62d5b6b1b19fb3cf241267917a875aba9 (diff) | |
| download | Qt-d1ce08936b4a6f4ce2b2e878287de76d47df0b8c.zip Qt-d1ce08936b4a6f4ce2b2e878287de76d47df0b8c.tar.gz Qt-d1ce08936b4a6f4ce2b2e878287de76d47df0b8c.tar.bz2 | |
Switched QtNetworkSetting to use 'qt-test-server' config by default.
Qt/Master uses qt-test-server config by default but our S60/master
was configure to use different server by default. The assumption is
that this caused several QtNetwork autotests to fail when testing
QtS60 branch on other configurations in QtSW premises. This because
the old test server was very likely unavailable...
Diffstat (limited to 'mkspecs/win32-borland')
0 files changed, 0 insertions, 0 deletions