| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | Change copyrights from Nokia to Digia4.5 | Sergio Ahumada | 2012-11-28 | 1 | -19/+18 |
| | | | | | | | | | Change copyrights and license headers from Nokia to Digia Change-Id: I9f5c8a9135271161e2bce50bc413ea01a08c3a76 Reviewed-by: Akseli Salovaara <akseli.salovaara@digia.com> Reviewed-by: Lars Knoll <lars.knoll@digia.com> | ||||
| * | Update license headers again. | Jason McDonald | 2009-09-08 | 1 | -4/+4 |
| | | | | | Reviewed-by: Trust Me | ||||
| * | Update tech preview license header. | Jason McDonald | 2009-08-31 | 1 | -13/+13 |
| | | | | | Reviewed-by: Trust Me | ||||
| * | Update license headers. | Jason McDonald | 2009-08-11 | 1 | -1/+1 |
| | | | | | Reviewed-by: Trust Me | ||||
| * | Fix crash when native socket notifiers would send a notification after being ↵ | Norwegian Rock Cat | 2009-07-20 | 1 | -4/+8 |
| | | | | | | | | | | | | | | | | | disabled. Spend a lot of time looking at this and at the CoreFoundation source code and it seems that we really do get a notification even after the notifier is disabled. I suspect there's a race condition between when we disable the socket notifier, but the kernel flags it as needing a read, then CoreFoundation just sends the notification without checking if the CFSocket has been disabled. No further notifications come of course. Since this breaks the invariant that was set in the assert, I'm replacing it with an if check. Task-number: 258198 Reviewed-by: Bradley T. Hughes | ||||
| * | Update license headers as requested by the marketing department. | Jason McDonald | 2009-06-16 | 1 | -2/+2 |
| | | | | | Reviewed-by: Trust Me | ||||
| * | Long live Qt 4.5! | Lars Knoll | 2009-03-23 | 1 | -0/+926 |
 |
index : qt/qt.git | |
| Qt 4.x. This repository is obsolete. |
| summaryrefslogtreecommitdiffstats |