[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Re: KDAT status
From:       Gabriele Gorla <gorlik () penguintown ! net>
Date:       2008-06-25 9:42:44
Message-ID: 1214386965.5384.6.camel () tux4 ! penguintown ! net
[Download RAW message or body]

Nicolas,
thanks for the help.
I started working on making kdat compile on kde 4.1 but it may take a
week or so. The code is very old and uses a lot of deprecated qt3
classes and old style iterators.

In the meantime I will request a svn access.

I also have a couple of patches for kdat on kde 3.5 that correct one
serious bug (the 99 byte block size) and enable drive hardware
compression.
Should I submit them to kde3? Only the bug fix, or both?

thanks,
GG

On Mon, 2008-06-23 at 09:44 +0200, Nicolas Ternisien wrote:
> On Mon, Jun 23, 2008 at 12:33 AM, Albert Astals Cid <aacid@kde.org> wrote:
> > I'm sure you forgot to say
> >
> > "Unless a maintainer is found"
> >
> > Albert
> >
> 
> Of course.... ;-)
> 
> 
> On Mon, Jun 23, 2008 at 1:04 AM, Gabriele Gorla <gorlik@penguintown.net> wrote:
> > Nicolas and Albert,
> > thanks for the replies.
> > I already have a few patches to fix the most annoying bug and to add
> > hardware compression. I also check out why is not compiling in KDE4.
> >
> > Please allow me another newbie question: if I were to volunteer to
> > maintain kdat, what do I need to do?
> >
> > thanks,
> > GG
> 
> You just need to do a simple thing : inform the Kdeadmin coordinator
> of being interested in maintaining Kdat, as you just did ;-)
> 
> Do not hesitate to commit patches to KDat, add your name in the About
> dialog, but do not reactivate the KDat build in the CMakeLists.txt of
> kdeadmin for the moment. This will be possible after the KDE 4.1
> release.
> 
> Regards.
> 
> Nicolas Ternisien

 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

[prev in list] [next in list] [prev in thread] [next in thread]