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

Re: enhancements for error reporting

From: Stefan Küng <tortoisesvn_at_gmail.com>
Date: Wed, 18 May 2011 18:50:58 +0200

On 18.05.2011 13:47, C. Michael Pilato wrote:
> On 05/18/2011 12:44 PM, Hyrum K Wright wrote:
>> On Wed, May 18, 2011 at 11:17 AM, C. Michael Pilato<cmpilato_at_collab.net> wrote:
>>> On 05/18/2011 09:53 AM, Bert Huijben wrote:
>>>> One obvious case is that libsvn_client sometimes suggests that you
>>>> should do a 'svn something', which is only possible if you use svn.
>>> libsvn_client should *never* give suggestions that refer to any particular
>>> client binary's usage semantics! If such cases exist today, those are bugs.
>> +1. And +1 to the notion of more granular error reporting, if required.
> I filed http://subversion.tigris.org/issues/show_bug.cgi?id=3887 to track
> the bogus error messages we already provided from the shared libs.
> I would strongly encourage Stefan to make good use of his project commit
> privileges to add the additional error codes that he deems necessary for
> TortoiseSVN. :-)

Assigned the issue to myself.

One question though:
there's one situation (the one that prompted me to start this thread)
though where I'm not sure if the error message should be changed:

libsvn_client/merge.c:8985: "...; try updating first"

This doesn't mention 'svn update' but the action itself. I'll change the
error code there so I can catch it in TSVN, but should the error message
change there too?


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