On Tuesday 18 June 2013 19:19:24 Albert Astals Cid wrote:
Sure we could do all that, but given the black magic that is involved in
startkde (or so I've been told), i'd prefer to go for a simpler solution
like the attached patch.
If anyone is running without qdbus on the path can you give
On Tuesday 18 June 2013 19:19:24 Albert Astals Cid wrote:
[snip]
There's also a check that the dbus session is available, but surely we'll
error out soon enough if this isn't the case?
Sure we could do all that, but given the black magic that is involved in
startkde (or so I've been told),
Hi all,
As some of you are aware, the physical host of git.kde.org and
svn.kde.org encountered some problems early in the morning (UTC time).
This has required that both are fully rebuilt.
At the moment, only git.kde.org has been restored to functionality -
however svn.kde.org will follow
Hi,
One of those not-strictly-technical things you might now want to miss is the
call for papers for the Qt DevDays to be held in Berlin (7-9 Oct) and San
Francisco (6-8 Nov). As KDE ist contributing more directly to Qt, and in fact
offering a lot of functionality on top of Qt (especially, but
---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/15/
---
Review request for kdelibs and David Faure.
Description
---
The
Hello,
On Tuesday 18 June 2013 17:23:15 Kevin Ottens wrote:
Announcements:
* Tomorrow no new patch should be started, instead we get all the pending
ones integrated so that dfaure can do a merge on thursday morning;
Due to git.kde.org being unreachable most of today, we're extending the
On 2013-06-17, Frank Reininghaus frank7...@googlemail.com wrote:
Yes, it can block for random reasons, and this is why making D-Bus
calls in the code that is executed before the context menu is shown is
unacceptable IMHO.
I agree with the problem. But the issue is to *fix* kactivities to not
On Mittwoch, 19. Juni 2013 20:21:41 CEST, Sune Vuorela wrote:
On 2013-06-17, Frank Reininghaus frank7...@googlemail.com wrote:
Yes, it can block for random reasons, and this is why making D-Bus
calls in the code that is executed before the context menu is shown is
unacceptable IMHO.
I agree
---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/110649/#review34706
---
This review has been submitted with commit
---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/110649/
---
(Updated June 19, 2013, 7:35 p.m.)
Status
--
This change has been
On 2013-06-19, Thomas Lübking thomas.luebk...@gmail.com wrote:
If I was a plugin developer here, I would of course think my plugin
should be enabled by default and thus in my ctor call
setEnabledByDefault(true)
I would suggest to leave the path of plugin enabling as solution asap - it's
not
---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/45/
---
Review request for kdelibs and David Faure.
Description
---
When
---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/110285/#review34718
---
Ship it!
Ship It!
- Andriy Rysin
On May 3, 2013, 11 a.m.,
13 matches
Mail list logo