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

Re: [PATCH] Issue 1628

From: SteveKing <steveking_at_gmx.ch>
Date: 2005-07-25 17:36:27 CEST

Mark Phippard wrote:

> Isn't brane's point that if say svnserve crashes it should not try to
> pop-up a send mail dialog which would only be seen if someone was logged
> in and looking for it? None of my Win2K3 servers have someone logged in.

But as soon as you log in, the dialog would be visible (or not?)

> You say that it can just save a zipped copy somewhere. That is excellent.
> Problem is you do not say how. Is that something that would have to be
> done with code, a config file, what? Along with brane's previous

The crash reporter is written as an UI for the user. The dialog has
three buttons:
Cancel : don't send the report and just quit the app
Save : save the zipped report somewhere and quit app
Send : open up a new mail window with the "to" address already
filled in and the zipped report already attached. The user then only has
to press "Send" in the mail program to send the report (but hopefully
writes a description about how/when/why the crash occurred).

> suggestion, maybe the command line could work one way and the servers
> another? Personally, I would be fine if it just dumped the crash to a
> file and in the case of the command line spit out some info as to where
> the file is located and where it can be mailed to.

As I said, this qould require a change in the crash reporter dll itself.
And since that dll is used for TSVN (and some of my other projects) I'm
happy with how it works now.


   oo  // \\      "De Chelonian Mobile"
  (_,\/ \_/ \     TortoiseSVN
    \ \_/_\_/>    The coolest Interface to (Sub)Version Control
    /_/   \_\     http://tortoisesvn.tigris.org
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Jul 25 17:38:34 2005

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

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