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

List:       kdelibs-bugs
Subject:    [frameworks-kio] [Bug 384561] Dolphin copy operation is 4,5x slower than cp
From:       Mahendra Tallur <bugzilla_noreply () kde ! org>
Date:       2018-02-11 22:09:50
Message-ID: bug-384561-90985-WPk7Ubg3dQ () http ! bugs ! kde ! org/
[Download RAW message or body]

https://bugs.kde.org/show_bug.cgi?id=384561

Mahendra Tallur <mahen@free.fr> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |mahen@free.fr

--- Comment #19 from Mahendra Tallur <mahen@free.fr> ---
Hi, thanks so much for the fix ! I was affected too but always thought the
issue was the USB stack or something else.

Regarding Nate, Massimo & Jaime's exchange : I must say, as a user and
occasional reporter, the bugtracker is a bit overwhelming. Despite my being
quite careful, I filed dozens of duplicates, which made me feel very bad. It
gave me the feeling of wasting the other volunteers' time. 

Some other times, I think I didn't file against the right component and the
bugreport was kinda lost.

So I'm wondering 
1) is there something in the bugtracker that is intrinsically misleading and 
adds work to triagers & devs ?
2) or should we help "educate" the users such as me so they file fewer reports,
fewer duplicates and target them properly ? 
3) the current "usability & productivity" campaign makes me extremely
enthusiastic. Could it set the groundwork for a long-term meta-organization of
the triaging / fixing work ?

Thanks again so much to everyone involved. Exciting times :-)

-- 
You are receiving this mail because:
You are on the CC list for the bug.=
[prev in list] [next in list] [prev in thread] [next in thread]