Attachment #130405 | |||||
---|---|---|---|---|---|
Add property averaging and presence setting to AccountSet, <> operators to Presence. | patch | 2017-03-23 23:04:31 UTC | 12.05 KB | no flags | Details |
Attachment #130684 | |||||
---|---|---|---|---|---|
Add property averaging, presence setting and account lookup by unique identifier to AccountSet, <> operators to Presence. | patch | 2017-04-05 06:22:41 UTC | 15.50 KB | no flags | Details |
Attachment #130685 | |||||
---|---|---|---|---|---|
Add property averaging, presence setting and account lookup by unique identifier to AccountSet, <> operators to Presence. | patch | 2017-04-05 06:36:21 UTC | 17.41 KB | no flags | Details |
Attachment #130887 | |||||
---|---|---|---|---|---|
Add property averaging, presence setting and account object export by unique identifier to AccountSet, <> operators to Presence | patch | 2017-04-18 03:58:00 UTC | 18.39 KB | no flags | Details |
Attachment #131717 | |||||
---|---|---|---|---|---|
Change the presence spec weighting for individual states | patch | 2017-06-05 17:43:37 UTC | 4.05 KB | no flags | Details |
Attachment #131718 | |||||
---|---|---|---|---|---|
Implement presence <> operators | patch | 2017-06-05 17:47:55 UTC | 1.67 KB | no flags | Details |
Attachment #131719 | |||||
---|---|---|---|---|---|
Add connection property averaging to AccountSet | patch | 2017-06-05 17:49:55 UTC | 13.33 KB | no flags | Details |
Attachment #131720 | |||||
---|---|---|---|---|---|
Export the AccountSet accounts as a QHash instead of a QList | patch | 2017-06-05 17:56:33 UTC | 5.90 KB | no flags | Details |
Attachment #131728 | |||||
---|---|---|---|---|---|
Add connection property averaging and presence setting to AccountSet | patch | 2017-06-05 21:59:43 UTC | 13.21 KB | no flags | Details |
Attachment #137599 | |||||
---|---|---|---|---|---|
Add connection property averaging and presence setting to AccountSet | patch | 2018-02-26 02:17:49 UTC | 15.52 KB | no flags | Details |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.