Mailing-List: contact dev-help@subversion.apache.org; run by ezmlm
Precedence: bulk
Received-SPF: neutral (athena.apache.org: local policy)
Date: Thu, 9 Oct 2014 12:05:04 +0200
From: Stefan Sperling <stsp@elego.de>
To: Branko =?utf-8?B?xIxpYmVq?= <brane@wandisco.com>
Cc: Subversion Development <dev@subversion.apache.org>
Subject: Re: Exception reporting
Message-ID: <20141009100503.GH17325@ted.stsp.name>
Mail-Followup-To: Branko =?utf-8?B?xIxpYmVq?= <brane@wandisco.com>,
	Subversion Development <dev@subversion.apache.org>
References: <864EF393C7D75842833B30FA560DE13D1F2AA0C8@SEMAIL.seamless.local>
 <543614AC.2020100@wandisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <543614AC.2020100@wandisco.com>
User-Agent: Mutt/1.5.23 (2014-03-12)

On Thu, Oct 09, 2014 at 06:53:00AM +0200, Branko Čibej wrote:
> On 08.10.2014 09:02, Kumar Krishnamoorthy wrote:
> >
> > Just reporting it because by subversion client asked me to report it :-)
> >
> 
> I'm beginning to wonder if we should ask the TSVN devs to field these
> crash reports. It's confusing and not very productive for us to get
> reports of crashes in Tortoise; I'm not saying these crashes "can't"
> have been caused by Subversion bugs, but it's IMO more efficient to the
> TSVN devs to do the initial triage and only forward actual bugs here.
> 
> Not to mention that it turns out that our Windows crash reporting hack
> is moderately useless, because it doesn't give the report enough context
> to do anything useful with the report.
> 
> -- Brane
> 

I agree. I've started to ignore all reports which provide no further
information than the naked crash report.