On Tuesday 14 July 2015 07:08:57 Andreas Cord-Landwehr wrote:
If it is OK this way, I can add it later today to the wiki page.
Hi, since I did not hear any oppositions, I just added the paragraph to the
wiki page draft.
Cheers,
Andreas
On Mon, Jul 20, 2015 at 05:08:45PM +0200, Daniel Vrátil wrote:
True, although the core code is mostly plain Qt wrapper around Xapian.
We've (me, Laurent and few people on #kontact) been using it for couple
weeks - months now without any problems.
Ok, I don't really have any objections.
--
Hi,
Can somebody help us with improving Krusader?
Thanks in advance for your help.
Beat regards,
Yuri
--- Переспрямоване повідомлення ---
Від: Toni Asensi Esteve asm...@gmx.com
Кому: krusader-de...@googlegroups.com
Копія:
Тема: [Krusader-devel] Help needed for Krusader .desktop files
I was thinking about reviving Kaffeine, but the previous developer hasn't
responded to me. The projects irc channel and sites are dead, too.
I was hoping someone here might be able to help me on this.
Lasse Lindqvist
If it's unmaintained and previous maintainer isn't responding go for
it. If you can get others interested in it enough to do review of your
updates, even better.
On Mon, Jul 20, 2015 at 12:01 AM, Lasse Lindqvist
lasse.k.lindqv...@gmail.com wrote:
I was thinking about reviving Kaffeine, but the
If you didn't read
https://mail.kde.org/pipermail/plasma-devel/2013-December/027399.html
the previous maintainer tried to find someone interested but
it seems nobody stepped up, so have fun :)
2015-07-20 3:01 GMT-03:00 Lasse Lindqvist lasse.k.lindqv...@gmail.com:
I was thinking about reviving
laurent Montel ha scritto:
Le Monday 20 July 2015, 22:58:39 Luigi Toscano a écrit :
Daniel Vrátil ha scritto:
Hi all,
we (the KDE PIM team) kinda screwed up when we forgot to communicate our
intentions about
next KDE PIM release with the release team and we ended up in a situation
that we
On Monday, July 20, 2015 04:17:16 PM Daniel Vrátil wrote:
Hi all,
we (the KDE PIM team) kinda screwed up when we forgot to communicate our
intentions about
next KDE PIM release with the release team and we ended up in a
situation that we have
some repositories in modules from which they
