---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/109384/
---
(Updated March 11, 2013, 1:18 p.m.)
Review request for Solid and Lukáš Tin
---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/109384/#review29073
---
This is not right. If you want to have a daemon, you should wri
> On March 12, 2013, 3:14 p.m., Dan Vrátil wrote:
> > This is not right. If you want to have a daemon, you should write a KDED
> > module and modify Solid (frontend or backends) to access the information
> > from the daemon.
I've just got an idea that it would be better if the daemon will be c
> On March 12, 2013, 4:14 p.m., Dan Vrátil wrote:
> > This is not right. If you want to have a daemon, you should write a KDED
> > module and modify Solid (frontend or backends) to access the information
> > from the daemon.
>
> Alexander Mezin wrote:
> I've just got an idea that it would
---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/109384/
---
(Updated March 14, 2013, 3:31 a.m.)
Review request for Solid and Lukáš Tin
---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/109384/#review29184
---
Please also test with special media, like blank and audio CDs.
> On March 14, 2013, 10:40 a.m., Lukáš Tinkl wrote:
> > Please also test with special media, like blank and audio CDs. Thanks for
> > the work!
I didn't touch code that handles other disk types, as only video disk detection
caused problems. And I don't have audio cds, sorry. But other people t
---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/109384/#review29211
---
The code looks fine, thanks!
There's another concern now, how
> On March 14, 2013, 3:02 p.m., Dan Vrátil wrote:
> > The code looks fine, thanks!
> >
> > There's another concern now, however (something that I haven't thought
> > about before, sorry!) - if the code now depends on kdelibs, we don't fit
> > Tear 1 in KDE Frameworks anymore. The question is
> On March 14, 2013, 3:02 p.m., Dan Vrátil wrote:
> > The code looks fine, thanks!
> >
> > There's another concern now, however (something that I haven't thought
> > about before, sorry!) - if the code now depends on kdelibs, we don't fit
> > Tear 1 in KDE Frameworks anymore. The question is
> On March 14, 2013, 3:02 p.m., Dan Vrátil wrote:
> > The code looks fine, thanks!
> >
> > There's another concern now, however (something that I haven't thought
> > about before, sorry!) - if the code now depends on kdelibs, we don't fit
> > Tear 1 in KDE Frameworks anymore. The question is
---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/109384/
---
(Updated March 19, 2013, 5:19 a.m.)
Review request for Solid and Lukáš Tin
---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/109384/
---
(Updated March 26, 2013, 3:17 p.m.)
Review request for Solid, Dan Vrátil a
---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/109384/
---
(Updated July 26, 2013, 7:52 p.m.)
Status
--
This change has been dis
14 matches
Mail list logo
