[PATCH] Klipper port to KConfigXT - patch or a feature?

Jordi Polo mumismo at gmail.com
Thu Nov 27 19:52:28 GMT 2008

With that enthusiasm towards klipper, It looks that klipper 4.2 will be more
bug free with that work than without it and we are in kill_bugs_mode (tm) so
I'd say merge.
I am not authoritative voice anyway, wait more answers.

On Fri, Nov 28, 2008 at 4:22 AM, Dmitry Suzdalev <dimsuzkde at gmail.com>wrote:

> On Thursday 27 November 2008 22:05:30 Sebastian K├╝gler wrote:
> > I'm tending towards "merge it", we're early enough in the cycle to
> warrant
> > such a cleanup and improve current code thing, provided:
> >
> > - the klipper maintainer wants it in (who's that?)
> I guess there's no active one at the moment.
> Lubos somewhat maintains it, but in fix-a-critical-bugs mode, if i'm not
> mistaken.
> > It's not a strong preferene, and I probably lack a good enough overview
> of
> > klipper to judge. Don't take this as a "sure, just commit". If you can
> > convince people that it indeed fixes crashers, then chances to get an OK
> > increase :)
> Ok, let's wait for other comments.
> I must add that i'm willing to fix any bugs this merge might introduce
> along with some more of its current bugs which i'll be able to fix.
> The other option is to commit bug fixes to the branch in which i did the
> conversion and then merge all these changes for 4.3.
> Dmitry.

Jordi Polo Carres
NLP laboratory - NAIST
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20081128/ec654500/attachment.htm>

More information about the kde-core-devel mailing list