Summary: | Several odd behaviours in KBlocks v. 0.3 | ||
---|---|---|---|
Product: | [Applications] kblocks | Reporter: | Jesper Goll <jesper> |
Component: | general | Assignee: | Zhongjie Cai <squall.leonhart.cai> |
Status: | RESOLVED NOT A BUG | ||
Severity: | normal | CC: | cfeck, kde-games-bugs |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | openSUSE | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Jesper Goll
2011-03-15 01:42:35 UTC
Thanks for the report, but could you please split each of these issues out into its own report? Combined reports like this are more difficult for developers to handle, as the issues can't be tracked individually. Just copying and pasting the descriptions from this report should be sufficient. Following the above request from Parker Coates, I have split this bug report into four new bugs: bug 268583 (for issue 1), bug 268581 (for issue 2), bug 268584 (for issue 3) and bug 268585 (for issue 4). As regards issue 5, that issue seems to have been already reported in bug 267859 - so in this case I added a comment to the existing bug. Done. I am unsure of what to do with the original bug, though. It can hardly be considered "solved" at this stage, nor does it seem to be in need of further info. I think it should be marked as "closed", but that option does not seem to be available. "Resolved as invalid" might do, I suppose...unless "invalid" is reserved for some other form of misery than the present one. If you feel like it, just change the status of bug 268528 to whatever it should be. News of your decision will reach me by the regular channels, I suppose. On 15-03-2011 14:48, Parker Coates wrote: > https://bugs.kde.org/show_bug.cgi?id=268528 > > > > > > --- Comment #1 from Parker Coates<parker coates kdemail net> 2011-03-15 14:48:04 --- > Thanks for the report, but could you please split each of these issues out into > its own report? Combined reports like this are more difficult for developers to > handle, as the issues can't be tracked individually. Just copying and pasting > the descriptions from this report should be sufficient. > I still prefer KSirtet because of all those issues :) Thanks. |