https://bugs.kde.org/show_bug.cgi?id=444750
Nate Graham changed:
What|Removed |Added
Status|CONFIRMED |RESOLVED
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=444750
--- Comment #6 from Ben Cooksley ---
They use the same Bugzilla instance as other Mozilla products -
https://bugzilla.mozilla.org/
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=444750
--- Comment #5 from Nate Graham ---
Do you have the URL for the upstream Bugzilla bug tracker where we can direct
users?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=444750
--- Comment #4 from Ben Cooksley ---
I would suggest closing this as RESOLVED/UPSTREAM as we generally prefer to
keep software completely unmodified unless it is completely necessary.
In this case, having to add attachments one by one while slightly an
https://bugs.kde.org/show_bug.cgi?id=444750
--- Comment #3 from Nate Graham ---
So in such a case, what should we do? Close the bug report as RESOLVED
UPSTREAM, even though we know that upstream is unlikely to be responsive? Or
keep it open in the hope that custom code modifications become accept
https://bugs.kde.org/show_bug.cgi?id=444750
Ben Cooksley changed:
What|Removed |Added
CC||bcooks...@kde.org
--- Comment #2 from Ben Cooksl
https://bugs.kde.org/show_bug.cgi?id=444750
Nate Graham changed:
What|Removed |Added
CC||n...@kde.org
Ever confirmed|0
https://bugs.kde.org/show_bug.cgi?id=444750
Ashark changed:
What|Removed |Added
CC||ash...@linuxcomp.ru
--
You are receiving this mail be