https://bugs.kde.org/show_bug.cgi?id=371934
--- Comment #4 from RJVB <rjvber...@gmail.com> --- Who remembers the days where 640Kb seemed a reasonable limit? ;) I'm a bit surprised the database would (still) use a hard length limit, but then I'm not a DB engineer and I guess KDE didn't write their own bug tracker from scratch. Either way: can remote clients query the system for the length limit? And on a more future note: how feasible would a be to implement a mechanism through which backtraces can be submitted as a backtrace with a standardised name, and then requested by remote clients like DrKonqi to use in searching for duplicate reports? I'm thinking of a custom entry field (like there are now for "steps to reproduce" and "Expected behaviour") which puts content entered there into an attachment with a standardised name, and a corresponding hook for remote clients to achieve the same thing. Does the tracker software have a search-for-duplicates feature one can evoke remotely, ideally one that knows about the backtrace formats used by the major debuggers? -- You are receiving this mail because: You are watching all bug changes.
