Josip Rodin wrote:
On Tue, Dec 20, 2011 at 02:51:08PM +0000, Mark Morgan Lloyd wrote:
I'm happy with that, but I'd suggest that it does need the more
experienced user/developers to ride herd on the rest of us, and when
somebody has an issue to say one of:
* That's a known issue which won't be changed for a good reason,
live with it.
* That's been reported already.
* That's new, report it.
The worst possible thing that can happen is for somebody who's got
hold of a SPARC-based system and is trying to find out whether it's
any use for anything to post a concern, to not get any feedback,
Well, that's unlikely, or at least the prospect of not getting feedback
after posting a bug report not any more unlikely compared to the prospect of
not getting feedback without posting a bug report :)
Let's cross that bridge when we get there. So far I've noticed that
bug #525718 has been mentioned in the thread - that one is long closed,
and people thought it was fixed back then (i.e. it wasn't unanswered).
A new bug report should be opened, and tagged sparc + severity grave, and
let's see where it goes :)
So who's going to bell the cat then? :-)
--
Mark Morgan Lloyd
markMLl .AT. telemetry.co .DOT. uk
[Opinions above are the author's, not those of his employers or colleagues]
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
Archive: http://lists.debian.org/[email protected]
