Dave Beck wrote:
Might
somebody from the Rev team reading this post be able to chime in about what
is needed in order to have this issue addressed properly?
Go here:
<http://support.runrev.com/bugdatabase/show_bug.cgi?id=3220>
Paste the content of one or more logs into the Comments field, or else
use the "create a new attachment" link to attach the logs. Click Commit.
If you get more logs, repeat. If the team needs to see your stack(s)
they can contact you. This is the best way to help the team track the
problem.
Alternately, you can enclose your logs in an email, along with a
description of the problem and a recipe to repeat it, which you can send
to support at <[EMAIL PROTECTED]>. This method may take a little longer
to process because it needs to wait in a queue until we move it to
Bugzilla manually, but it is an acceptable way to report a problem and
the lag isn't excessive.
--
Jacqueline Landman Gay | [EMAIL PROTECTED]
HyperActive Software | http://www.hyperactivesw.com
_______________________________________________
use-revolution mailing list
[email protected]
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
