or features you not use
yourself at all),
any meaningful review is a full-time job. e.g. in our company you would let
some student
test the changed behavior some days. This is just not feasible for me, and yes,
for some of these changes, rather than abandoning them (and trashing precious
work
just be ticked of.
For the licensing, Jonathan, is it ok to remove the TODO there and say "OK"?
Perhaps some link to a mail to an public list would be nice there.
Greetings
Christoph
--
----- Dr.-Ing. Christoph Cullmann -
AbsInt Angewandte Informatik
Hi,
> On Fri, Oct 7, 2016 at 6:14 PM, Christoph Cullmann
> wrote:
>>>>
>>>
>>> I don't understand why all framework discussions must happen on the
>>> same list. It just adds to a crazy amount of noise, which one then
>>> needs to
cussions must happen on the
> same list. It just adds to a crazy amount of noise, which one then
> needs to parse through.
If you would have baloo-devel I could understand that point,
but not with some other generic mailing list like kde-devel which
has the same amount of noise and is not ev
rg/?p=clones%2Fbaloo%2Fcullmann%2Ftbaloo.git
That is just a proposal and then I started the discussion.
Until now, we have one other proposal, by Boudhayan, to fixup baloo.
>
> (If the discussion continues on kde-frameworks-devel, I probably won't see it)
I won't see it on kde-dev
ustomization/entities/contributor.entities
> +++ /dev/null
> @@ -1,527 +0,0 @@
> - Zé
>
> >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to
> >> unsubscribe <<
>
--
-- Christoph Cullmann -
AbsInt Angewandte In
On Tuesday, July 12, 2011 10:36:05 AM David Jarvie wrote:
> On Mon, July 11, 2011 8:40 pm, Christoph Cullmann wrote:
> > On Monday, July 11, 2011 09:32:10 PM Ingo Malchow wrote:
> >> Please don't reply to that as of now, it looks quite strange. Needs to
> >> be con
On Monday, July 11, 2011 09:32:10 PM Ingo Malchow wrote:
> Please don't reply to that as of now, it looks quite strange. Needs to
> be confirmed. And to be remembered, we don't "sell" link exchanges nor
> do we accept those.
Read my other mail here, he is a known farmer and tries that with multiple
Hi all,
don't waste your time with this request for translation.
And don't ever call or link him!
He is a scammer/pisher/whatever, he mailed the gcc list, too, with two
different names (but same telephone number). And he mail me today, too.
Same trick for kate-editor.org
Greetings
Christoph
On Thursday, May 19, 2011 12:34:49 pm Christoph Cullmann wrote:
> On Thursday, May 19, 2011 11:06:23 am Hugo Pereira Da Costa wrote:
> > On 05/19/2011 10:57 AM, Lydia Pintscher wrote:
> > > On Thu, May 19, 2011 at 08:09, Hugo Pereira Da Costa
> > >
> > > wrot
ng mode". we do consult bko on a
> regular basis and address issues there.
I just reopened https://bugs.kde.org/show_bug.cgi?id=245807
Anyone interested can CC himself there, CCed hugo.
Greetings
Christoph
--
-- Christoph Cullmann -
AbsInt Angewand
Am Mittwoch, 18. Mai 2011, 00:41:40 schrieb David Jarvie:
> On Tuesday 17 May 2011 19:33:15 Christoph Cullmann wrote:
> > Am Dienstag, 17. Mai 2011, 19:03:41 schrieb Albert Astals Cid:
> > > A Tuesday, May 17, 2011, Martin Gräßlin va escriure:
> > > > @all: please
Am Dienstag, 17. Mai 2011, 19:03:41 schrieb Albert Astals Cid:
> A Tuesday, May 17, 2011, Martin Gräßlin va escriure:
> > @all: please keep the emotions out of this thread and be constructive. I
> > offered a possible solution for the "problem" yesterday and nobody seems
> > to be interested in act
opinion, I can only conclude:
Commercial vendors of Qt software must enforce an own style and not use the
set default, otherwise their applications might break, even with a default KDE
desktop.
And no, bug report forwarding doesn't help at all, if you are no open-source
applicati
On Monday, May 16, 2011 09:55:22 am Alex Fiestas wrote:
> On Monday, May 16, 2011 07:52:26 AM Christoph Cullmann wrote:
> > Beside I doubt that 3rd-party Qt application developers want to work
> > around that issue. That really should be an optional setting (maybe even
> >
h tap-to-click enabled.
Beside I doubt that 3rd-party Qt application developers want to work around
that issue. That really should be an optional setting (maybe even with warning
the user that this can result in interesting behaviour for some applications)
Greetings
Christoph
--
-
16 matches
Mail list logo
