[PATCH] drkonqi: s/backtrace/backtrace full/g

Chris Howells howells at kde.org
Tue Jan 27 11:06:31 GMT 2004


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

On Tuesday 27 January 2004 10:00, Russell Miller wrote:
> "A full backtrace may allow the maintainer to track down and find the bug
> more quickly, but at the expense of requiring more CPU power and memory to
> generate it.  Would you like a full backtrace?"

I think this is completely unnecessary. What normal sane user is going to know 
what the a backtrace is?

I don't see this as being an issue anyway; you only get the backtrace if you 
click on the backtrace tab and it's not difficult to cancel it in the middle.

- -- 
Cheers, Chris Howells -- chris at chrishowells.co.uk, howells at kde.org
Web: http://chrishowells.co.uk, PGP ID: 0x33795A2C
KDE/Qt/C++/PHP Developer: http://www.kde.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (FreeBSD)

iD8DBQFAFkZAF8Iu1zN5WiwRAjmtAKCVrogKYq/QZ4VEKfTfsmoVQDUeHwCeK/Nz
qyYHK7twUFp//WgLp/5UU+U=
=QK4I
-----END PGP SIGNATURE-----




More information about the kde-core-devel mailing list