OK, teach a man to fish - is much easier to teach how to file a report.
Therefore, just like in a computer class - I expect to see a VERY ELABORATE and DETAILED - written - procedure - on how to file a report.
In my hay-day, in a professional IT job, I wrote very elaborate and detailed - Operator, Application Programmer, Systems Programmer, Management procedures.
In almost every place I was at, I was in charge of writing the - DISASTER RECOVERY - procedures for the companies - even some from COMPLETE SCRATCH.
The largest on I wrote was about - 100 pages - 8.5x11 - double spaced - typed.
AND was fully TESTED - BY THE OPERATORS - and PROVED to be complete because we went to an IBM Disaster site in Boulder, CO - and - the procedure worked perfectly.
SO, I know a half-ass-ed procedure when I see one. Careful you don't hurt yourself patting yourself on the back like that. If you're so good at it, why don't YOU go file the report? I don't know
the details he's encountering for his problem, so how could I write such a report and submit it? But since it's what you evidentally are so good at, why don't YOU go do it. Or stop bitching that people are saying to file bugs.
Go to it and send it to me for approval, Duaine .....time to come down off that high horse don't you think?
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org