> On Dec. 9, 2013, 12:01 p.m., Dario Freddi wrote:
> > To be completely honest, the QPointer crash doesn't make sense at all and
> > sounds more like an actual Qt bug more than a PolkitKCM bug. I don't think
> > that would be a good solution in the big picture.
> >
> > That said, it's also tru
---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/113360/
---
(Updated Dec. 10, 2013, 6:47 p.m.)
Status
--
This change has been mar
---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/113360/#review45497
---
This review has been submitted with commit
dbfa291938b1990b01c
---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/113360/#review45380
---
Ship it!
To be completely honest, the QPointer crash doesn't m
---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/113360/
---
(Updated Dec. 8, 2013, 10:45 a.m.)
Review request for kde-workspace, Polki
---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/113360/
---
(Updated Oct. 27, 2013, 10:01 p.m.)
Review request for kde-workspace and P
