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

RE: [PATCH] libsvn_client/status.c

From: Bill Tutt <rassilon_at_lyra.org>
Date: 2001-09-24 17:18:59 CEST

Bah. Always display network error messages. Even if you can continue on
without it.

At minimum you could do something like:
Warning: Couldn't connect to repository
Warning: error text goes here

Hiding network connection errors are just going to frustrate the user,
esp. when network errors can take several seconds to time out. If these
things were always instantanious, or something else quck to fail, then I
wouldn't mind so much, but network communications errors really should
always be reported.
Even if they're treated as warnings.


-----Original Message-----
From: Ben Collins-Sussman [mailto:sussman@collab.net]
Sent: Monday, September 24, 2001 8:01 AM
To: svn@subversion.tigris.org
Subject: Re: [PATCH] libsvn_client/status.c

"Bill Tutt" <rassilon@lyra.org> writes:

> Ditto, I certainly failed to grasp why you'd ever want to ignore a
> network communication error....

Because if I run 'svn status' and the network fails for some reason, I
still want to see local mods. Better to have half the information than
return a gross error to the user.

To unsubscribe, e-mail: svn-unsubscribe@subversion.tigris.org
For additional commands, e-mail: svn-help@subversion.tigris.org

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Oct 21 14:36:42 2006

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.