Crash report timeout

Hi Stefan,

I notice in the issue tracker that you have put a 3 month time limit
on crash reports. That set me thinking about different ways of cutting
down crash reports, or at least filtering them out.

Is it possible to create some sort of hash based on the stack trace so
that a particular type of crash can be uniquely identified? I'm saying
this as one who has never used VC++ so I don't know if this is even
possible. But if it is, you could add that key to the crashreport
subject line and get your mail client to filter out all the known
fixed reports. It could also be used as a query term on our website;
the crash reporter could provide a link to our site which would tell
them whether or not that bug is fixed. If it is, there is no need to
send the crash report at all, and the user can be told where to
download the new version (if available), or what the workaround is (if
not).

Simon

-- 
       ___
  oo  // \\      "De Chelonian Mobile"
 (_,\/ \_/ \     TortoiseSVN
   \ \_/_\_/>    The coolest Interface to (Sub)Version Control
   /_/   \_\     http://tortoisesvn.net
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org