---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/120062/
---
Review request for KDE Frameworks, Christoph Cullmann, Kevin Ottens, and
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/120062/
---
(Updated Sept. 5, 2014, 8:39 a.m.)
Review request for KDE Frameworks,
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/120062/#review65825
---
For me it's better.
I like it.
For me Ship it is a good idea
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/120062/#review65826
---
Looks like good idea.
- Christoph Cullmann
On Sept. 5,
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/119798/#review65841
---
Sorry to still be nitpicking documentation, but I view it as
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/120058/
---
(Updated Sept. 5, 2014, 4:56 p.m.)
Review request for KDE Frameworks.
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/119594/
---
(Updated Sept. 5, 2014, 7:01 p.m.)
Status
--
This change has been
On Tuesday 02 September 2014 11:06:02 Luca Beltrame wrote:
In data martedì 19 agosto 2014 21:48:04, David Faure ha scritto:
I'd pick option 1 - do it all in ksmserver.
I suppose this would mean running all but .desktop files (which are handled
by kinit)?
I thought all was clear ;)
I see no
Hi!
I get this error when building KService. I don't quite get it, what it
means. Could someone help me deciphering the error?
Thanks!
David Gil
# kdesrc-build running: 'make' '-j2'
# from directory:
/home/david/devel/kf5-development/build/frameworks/kservice
Scanning dependencies of target
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/119936/#review65863
---
Ship it!
src/services/kplugininfo.h
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/119975/#review65864
---
Ship it!
Ship It!
- David Faure
On Aug. 28, 2014, 3:57
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/119970/#review65866
---
Ah wait, I do: lots of @since 5.2 missing in api docs.
And a
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/120071/#review65867
---
Ship it!
Ship It!
- David Faure
On Sept. 5, 2014, 6:31
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/120075/
---
Review request for KDE Frameworks.
Repository: karchive
Description
On Friday 05 September 2014 23:48:24 David Gil Oliva wrote:
In file included from /usr/include/kexportplugin.h:21:0,
/usr/include/kglobal.h:4
It's picking up kdelibs4 headers from /usr/include.
Easy solution: remove kdelibs4-dev or whatever that package is called.
Correct solution: make
See http://build.kde.org/job/frameworkintegration_master_qt5/105/changes
___
Kde-frameworks-devel mailing list
Kde-frameworks-devel@kde.org
https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
On Sept. 2, 2014, 6:37 p.m., Marco Martin wrote:
I'm a bit worried by the multitude of user and distro specific scripts that
rely on kdesu being present :/
Marco Martin wrote:
to me either way it gets fixed i'm ok.
the other option is to keep it called kdesu, so it wouldn't be
See
http://build.kde.org/job/kwindowsystem_master_qt5/Variation=All,label=LINBUILDER/changes
___
Kde-frameworks-devel mailing list
Kde-frameworks-devel@kde.org
https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
On Sept. 1, 2014, 7:55 vorm., David Faure wrote:
You wrote: I have not yet completely grasped the concept of the default
shortcuts and why they are set only explicitely via
KActionCollection::setDefaultShortcuts.
I think the concept is simple. QAction only knows the current
On Sept. 6, 2014, 12:07 vorm., David Faure wrote:
Between KService, KPluginInfo (.desktop) and KPluginMetaData (json) (all of
which represent a plugin), it's getting a bit confusing :)
But I can't see anything wrong in this commit :)
My plan is to implement KPluginInfo based on
On Sept. 5, 2014, 11:58 nachm., David Faure wrote:
src/services/kplugininfo.cpp, line 95
https://git.reviewboard.kde.org/r/119936/diff/4/?file=308036#file308036line95
can't that lead to a crash if people use other methods after that?
Well, it is the same as when KPluginInfo is
21 matches
Mail list logo
