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

Re: Question regarding bug report 3148: Too early svn up/co abort if one item of svn:externals resource list is not accessible

From: Karl Fogel <kfogel_at_red-bean.com>
Date: Tue, 05 Aug 2008 17:53:51 -0400

Achim.Spangler_at_mnet-online.de writes:
> Do you have any other idea to issue a warning from library to
> application - instead of the normal error message?
> An "svn up" should continue with other "svn:externals" items, even if
> another previously checked "svn:externals" item triggers an error.
> So - should I implement chaining individual error log entries per
> processed "svn:externals" and then return the error-chain at the end
> of "handle_externals_desc_change()"?

I think the way to do this is to collect ("accummulate") the errors into
a chain, and return that chain at the end, with a specified leading
error that is documented to mean "errors were encountered while
processing externals". Then the caller can identify the nature of the
chain easily, and handle it however it wants, including by displaying a

By the way, this is similar to the problem I was having with


...which I discussed further in the thread linked to from here:



To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-08-05 23:54:07 CEST

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.