[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: SVN 1.6.12 crash on merge.

From: Daniel Shahaf <d.s_at_daniel.shahaf.name>
Date: Wed, 25 Aug 2010 01:35:29 +0300

Lieven Govaerts wrote on Tue, Aug 24, 2010 at 20:53:55 +0200:
> On Tue, Aug 24, 2010 at 8:26 PM, Andy Levy <andy.levy_at_gmail.com> wrote:
> > On Tue, Aug 24, 2010 at 08:55, Pavel Ivanov <Pavel.Ivanov_at_acronis.com> wrote:
> >>
> >
> > When reporting a crash, it is much more helpful if you can attach a
> > sample repository & exact steps (preferably a script) which will
> > reliably reproduce the issue. Just attaching dumps & logs without
> > explaining how you got there is going to make things difficult for
> > someone trying to help you.
>
> If companies/people offering windows cmd-line client binaries build an
> unchanged subversion (which is what I expect them to do) then users
> will see the standard windows crash reporter message, which asks them
> to send the crash log file to this mailing list.
>
> I agree with your point, a reproduction recipe would be helpful. We
> could probably be a bit more explicit about this in our message to the
> users.
>

Don't we have some how-to-report-a-bug.html page already?

> Lieven
Received on 2010-08-25 00:38:44 CEST

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.