https://bugs.kde.org/show_bug.cgi?id=447119
--- Comment #19 from tagwer...@innerjoin.org --- (In reply to cybea from comment #18) > ... To me this looks like many bugs and having only one bug report could make > tracking and prioritizing harder. But I appreciate having this overview ... I can see that, what was happening though was we had been drowning under a wave of overlapping reports. If there's a new report, we have the choice of flagging it as a duplicate or leaving it and cross-referencing with a "see also". There is, I think, the possibility of creating a "tracking bug" that gets resolved when all the component issues are resolved. I've no experience of these and am not sure whether it would be appropriate here... -- You are receiving this mail because: You are watching all bug changes.
