Wild guess - probably, he expected, that such experimental stuff will be installed only by people that know already, hot to report problems properly (or how to ask about how to report properly, before reporting ).

Still, at current state, CSSU-Thumb is - in practice - CSSU testing (and cssu-testing is cssu-stable, due to various ambient conditions, like way CSSU-mainline is maintained, etc - out of topic here), and, frankly, we have "stable" i thread title here.

While I know that this doesn't mean "c'mon here and install it right now, everyone!", it's natural, that everyone want to experience thumb2's and upgraded compiler's benefits.

So, summing it up, I agree, that in current conditions, adding mandatory lecture about proper reporting of problems, could be beneficial. Some would read it, for others, it would be enough to post link as a reply (instead of repeating self over and over), and who knows, maybe other projects would link to those instructions too...

/Estel

// Edit

I planned to jump into writing such tutorial right now, but, as my comment on timeline of syslog/dmesg output shows, my "expertise" on the matter, may be not up to the task. I wouldn't like to cause much trouble/confusion by messing something up, that's why I think it would be better, if freemangordon would write such guidelines himself. I'll gladly pack it, then, into wiki page.