Please reply to all to keep discussion on the mailing list.
On Fri, Aug 19, 2011 at 07:48, Joel Hughes <joel.l.hughes_at_gmail.com> wrote:
> Hey, I'm just following the directions provided when it happened. I thought
> it was pretty useless as well. Perhaps instead you should provide a url
> which further explains all the details you would like and in what format.
> The address provided for sending the dumps was generic so I figured it was
> automatically routing them and if I added more to the mail it would mess up
> the parsing and not get routed.
> I'll provide you a proper mail a little later.
Your first step in reporting an issue should be, unless you can
determine for certain that the source code hasn't been changed from
the official source, to report it to the maintainers of the particular
client you're using. And again, simply mailing a crash dump with no
additional information does not provide anyone with enough information
to help you.
The address you've sent the email to is neither "generic" nor
"automatically routed" - it is for discussion by & for users of
As I said before, there *have* been reports of problems with at least
one version of SlikSvn (see http://tinyurl.com/3tc2nss for references
to SlikSvn on this list), but since you've not posted what version
you're using, no one here can help you in that regard.
> On Fri, Aug 19, 2011 at 6:39 AM, Andy Levy <andy.levy_at_gmail.com> wrote:
>> On Thu, Aug 18, 2011 at 10:51, Joel Hughes <joel.l.hughes_at_gmail.com>
>> There is at least one known glitchy release of SlikSvn out there.
>> A crash dump is almost useless if there's no description of what you
>> were doing to make it happen. You can't just dump a logfile off to a
>> mailing list and expect something to be done with it.
>> This is better directed at the SlikSvn team, as they compile their own
>> binaries from the source distributed by this project.
Received on 2011-08-19 16:01:26 CEST