---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/121095/
---
(Updated Nov. 14, 2014, 1:33 p.m.)
Status
--
This change has been
On Nov. 11, 2014, 2:39 p.m., Albert Astals Cid wrote:
I sincerely think this is a *VERY BAD* idea. I don't want my app behaving
differently depending if a third party misterious compononent that is not
documented anywhere is installed or not. If you have a dependency, well put
it in
On Nov. 11, 2014, 2:39 p.m., Albert Astals Cid wrote:
I sincerely think this is a *VERY BAD* idea. I don't want my app behaving
differently depending if a third party misterious compononent that is not
documented anywhere is installed or not. If you have a dependency, well put
it in
On nov. 11, 2014, 2:39 p.m., Albert Astals Cid wrote:
I sincerely think this is a *VERY BAD* idea. I don't want my app behaving
differently depending if a third party misterious compononent that is not
documented anywhere is installed or not. If you have a dependency, well put
it in
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/121095/#review70302
---
Since this seems quite easy to test, I would like automated
On nov. 11, 2014, 2:39 après-midi, Albert Astals Cid wrote:
I sincerely think this is a *VERY BAD* idea. I don't want my app behaving
differently depending if a third party misterious compononent that is not
documented anywhere is installed or not. If you have a dependency, well put
On Nov. 11, 2014, 2:39 p.m., Albert Astals Cid wrote:
I sincerely think this is a *VERY BAD* idea. I don't want my app behaving
differently depending if a third party misterious compononent that is not
documented anywhere is installed or not. If you have a dependency, well put
it in
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/121095/#review70233
---
src/integrationplugin/frameworkintegrationplugin.cpp
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/121095/
---
(Updated Nov. 11, 2014, 1:12 p.m.)
Review request for KDE Frameworks.
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/121095/#review70236
---
Perhaps add a framework guy to this request (and other
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/121095/#review70238
---
I sincerely think this is a *VERY BAD* idea. I don't want my
On Nov. 11, 2014, 3:39 p.m., Albert Astals Cid wrote:
I sincerely think this is a *VERY BAD* idea. I don't want my app behaving
differently depending if a third party misterious compononent that is not
documented anywhere is installed or not. If you have a dependency, well put
it in
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/121095/
---
(Updated Nov. 11, 2014, 3:51 p.m.)
Review request for KDE Frameworks,
On nov. 11, 2014, 2:39 p.m., Albert Astals Cid wrote:
I sincerely think this is a *VERY BAD* idea. I don't want my app behaving
differently depending if a third party misterious compononent that is not
documented anywhere is installed or not. If you have a dependency, well put
it in
On Nov. 11, 2014, 3:39 p.m., Albert Astals Cid wrote:
I sincerely think this is a *VERY BAD* idea. I don't want my app behaving
differently depending if a third party misterious compononent that is not
documented anywhere is installed or not. If you have a dependency, well put
it in
On nov. 11, 2014, 2:39 p.m., Albert Astals Cid wrote:
I sincerely think this is a *VERY BAD* idea. I don't want my app behaving
differently depending if a third party misterious compononent that is not
documented anywhere is installed or not. If you have a dependency, well put
it in
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/121095/
---
Review request for KDE Frameworks.
Repository: frameworkintegration
17 matches
Mail list logo
