https://bugs.kde.org/show_bug.cgi?id=340982
--- Comment #198 from cat22 <erben...@comcast.net> ---
(In reply to Nate Graham from comment #197)
> The bug is acknowledged. It's marked as CONFIRMED with a VHI ("very high")
> priority and various technical people have shown up to offer thoughts on how
> to proceed with resolving it. At this point the best way to make that happen
> is to let them have that conversation without adding a bunch of comments
> saying things like, "+1, this is so bad!" and "OMG how did you let this
> happen?!" "and I've given up hope, KDE sux". Yes, we know it's bad, but
> clearly there is some desire to fix it among the developers. So let's let
> that happen.
>
> If you want to express your feelings about how bad this is and urge a
> quicker resolution, feel free to send them directly to me at n...@kde.org
> instead of posting a comment.
>
> Thanks.
and yet, nothing has been done in 7 years so apparently
CONFIRMED with a VHI ("very high") priority
don't mean what it says?
My guess is no one is even looking at this or just dismissing it as "to
involved or to hard"
To me, i would think it shouldn't take more than writing a function that does
the work
and a few lines of code to decide whether to call it or not. It just can't be
so difficult that
someone couldn't fix it in an afternoon.
Be honest and change the status to "WILL NOT FIX" and we can be done with this
bickering
--
You are receiving this mail because:
You are watching all bug changes.
