RE: svn commit: r1501371 - /subversion/trunk/subversion/libsvn_ra_serf/util_error.c
From: Bert Huijben <bert_at_qqmail.nl>
Date: Tue, 9 Jul 2013 23:51:09 +0200
> -----Original Message-----
Which requires tools to start message scraping?
My Chinese error parser is not so good, and perhaps somebody changes the .po file with the next patch release?
TortoiseSVN, VisualSVN, AnkhSVN and probably most other GUI clients prefer error values over texts.
The texts are for our users and should tell them enough without them ever looking at the error values.
So: What are we talking about here?
An 'svn'-only user wants to see different error codes?
(Perhaps he added patch over patch to make the numbers more visible in MAINTAINER mode?)
100% agree on: The message should be set before the user sees the error.
But I fail to see why wrapping every error in generic subversion errors is going to help anybody.
Should I handle these error messages by pointing them to specific e-mail addresses?
These codes add value to our bindings... It allows more advanced bindings to use this knowledge.
This is an archived mail posted to the Subversion Dev mailing list.