-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

> broken... a NEW kde frontend needs to be rewritten, or at least the
> errors must be found, instead of saying that nothing is wrong. i don't
> mean by this to say that a licq developer is obliged to fix this, bla
> bla, i know this is a free time project, i just meant to say that the
> licq kde frontend IS broken for some ppl, and it's unreasonable to ask
> for someone to change of kde because licq doesn't work. I know, i can
> use something else, but that won't fix the bugs will it?:)

but in the other hand remember that these are mandelbugs.
the nature of the bug (for example i have the same setup as many reports 
kde-gui, kde 3.01 or kde3.1 alpha etc,etc and it doesnt crush) make it 
difficult to fix. (how some one can fix it with out the problem)(yes its 
not imposible but is a hard problem)

bah. thats my thought as an user. 
-----BEGIN PGP SIGNATURE-----

iD8DBQE9PvJAUMlRieHkprgRAoawAJ9xYm+0uhh5KuRLmMUNHpJSf4b8EACeOXGN
A5VV0wTVZatdqA8I5eVzBmI=
=L2v4
-----END PGP SIGNATURE-----



-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Licq-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/licq-devel

Reply via email to