---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/122953/
---
(Updated March 14, 2015, 8:23 p.m.)
Status
--
This change has been m
> On March 14, 2015, 8:10 p.m., Jeremy Whiting wrote:
> > I'm not sure I understand what this is for. If you try to build with
> > knewstuff and kio and karchive aren't present, it wont run properly. Is
> > this to make stuff that uses knewstuff build when the dependencies are
> > there, but t
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/122953/#review77476
---
Ship it!
Ship It!
- Jeremy Whiting
On March 14, 2015, 1:06
> On March 14, 2015, 8:10 p.m., Jeremy Whiting wrote:
> > I'm not sure I understand what this is for. If you try to build with
> > knewstuff and kio and karchive aren't present, it wont run properly. Is
> > this to make stuff that uses knewstuff build when the dependencies are
> > there, but t
> On March 14, 2015, 7:10 p.m., Jeremy Whiting wrote:
> > I'm not sure I understand what this is for. If you try to build with
> > knewstuff and kio and karchive aren't present, it wont run properly. Is
> > this to make stuff that uses knewstuff build when the dependencies are
> > there, but t
> On March 14, 2015, 8:10 p.m., Jeremy Whiting wrote:
> > I'm not sure I understand what this is for. If you try to build with
> > knewstuff and kio and karchive aren't present, it wont run properly. Is
> > this to make stuff that uses knewstuff build when the dependencies are
> > there, but t
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/122953/#review77472
---
I'm not sure I understand what this is for. If you try to buil
