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

enhancements for error reporting

From: Stefan Küng <tortoisesvn_at_gmail.com>
Date: Tue, 17 May 2011 20:54:32 +0200


Currently the svn command line client prints out (sometimes, if it's
possible) some helpful messages telling the user what to do, e.g., run a
cleanup or try an update.

The problem I have in TSVN is that in most situations, the error code
that's returned is not specific enough. For example, the error code
SVN_ERR_CLIENT_NOT_READY_TO_MERGE is not just used if the working copy
is out of date and needs updating, but also if the revision of the
working copy can not be determined, if a subtree is switched, the wc has
local modifications or if it's not 'ancestrally related'.
So in TSVN I can not use the error code to offer the user to just run an
update and retry the merge, or run cleanup and retry whatever command
failed because of that.

Could the error baton be extended to contain "action codes" that
indicate what action(s) need to be done to (probably) resolve the error?


   oo  // \\      "De Chelonian Mobile"
  (_,\/ \_/ \     TortoiseSVN
    \ \_/_\_/>    The coolest Interface to (Sub)Version Control
    /_/   \_\     http://tortoisesvn.net
Received on 2011-05-17 20:55:04 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.