> On April 30, 2014, 1:29 p.m., Alex Merry wrote:
> > Well, it looks like nothing that has been ported is using it (and barely
> > anything that hasn't been ported ever used it).
> >
> > However, it should be marked as deprecated, and the apidocs should
> > indiciate how to port away from it.
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/117888/
---
(Updated May 4, 2014, 8:29 p.m.)
Status
--
This change has been mark
> On April 30, 2014, 12:29 p.m., Alex Merry wrote:
> > Well, it looks like nothing that has been ported is using it (and barely
> > anything that hasn't been ported ever used it).
> >
> > However, it should be marked as deprecated, and the apidocs should
> > indiciate how to port away from it.
> On April 30, 2014, 12:29 p.m., Alex Merry wrote:
> > Well, it looks like nothing that has been ported is using it (and barely
> > anything that hasn't been ported ever used it).
> >
> > However, it should be marked as deprecated, and the apidocs should
> > indiciate how to port away from it.
> On April 30, 2014, 1:29 p.m., Alex Merry wrote:
> > Well, it looks like nothing that has been ported is using it (and barely
> > anything that hasn't been ported ever used it).
> >
> > However, it should be marked as deprecated, and the apidocs should
> > indiciate how to port away from it.
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/117888/#review56981
---
Well, it looks like nothing that has been ported is using it (
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/117888/
---
Review request for KDE Frameworks.
Repository: kdelibs4support
Descript