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

List:       kde-panel-devel
Subject:    Re: DrKonqi and BKO
From:       Harald Sitter <sitter.harald () gmail ! com>
Date:       2016-11-02 10:32:50
Message-ID: CAEc+18G0qk9CCgyDmr4uwPfCKhBL9dPbg+b+tGnhp82Wtbr+fw () mail ! gmail ! com
[Download RAW message or body]

On Wed, Nov 2, 2016 at 11:04 AM, Ren=C3=A9 J. V.  Bertin <rjvbertin@gmail.c=
om> wrote:
> Martin Klapetek wrote:
>
>
>> For improving readability, there is bugzilla-traceparser plugin, that ca=
n
>> dynamically
>> hide looooooooong backtraces with a bit of JS magic to expand them and m=
uch
>> more
>> like finding duplicates and also auto-dupe. I still think this would hel=
p
>> tremendously to
>> all our bugzilla users.
>
> Yes, long inline backtraces do not make it easier to navigate a bug repor=
t.
>
> Still, the best thing would be a formal way to attach a backtrace, e.g. a=
s an
> attachment with a standardised name. I'm thinking of a dedicated entry fi=
eld on
> the bug entry webpage and programmatic hooks to upload and query these
> attachments.

Bug trackers are not trace trackers. Spending time on solving the
actual problem is the best thing https://retrace.fedoraproject.org/
https://errors.ubuntu.com/
[prev in list] [next in list] [prev in thread] [next in thread]