https://bugs.kde.org/show_bug.cgi?id=355390
--- Comment #8 from Frank Reininghaus <frank7...@googlemail.com> --- (In reply to Yuriy Kolesnikov from comment #7) > Frank, please eplain your decision why this report this report form > 2015-11-15 was marked as duplicate of report from 2015-12-01. In the future, please just add a comment to the other report which contains the information that you think is missing there. Reopening reports and demanding explanations is a huge waste of everyone's time, and lack of time is the main reason for the sad state of bugs.kde.org. Thanks! > This report has more comments and relevant information. The backtrace is the most relevant information. The other report has one pasted inline, which means that one can search for its contents with the advanced search. this one only has an attached backtrace, which means that searches will not find anything in it. Yes, I could have copied the attached backtrace and pasted it in a new comment and then marked the other report as a duplicate of this one. However, I thought that the solution which I chose (namely, to mark your report as a duplicate) takes less time. Note that there is no rule that says that newer reports must be marked as duplicates of older ones. -- You are receiving this mail because: You are watching all bug changes.
