Pssst... file the issue. On 01/26/2011 01:24 PM, Daniel Shahaf wrote: > Julian Foad wrote on Wed, Jan 26, 2011 at 17:35:43 +0000: >> Two other suggestions for what we could do to improve the situation. >> >> * Make "svn" print a consistent error string for "does not exist in >> revision R" errors, regardless of subcommand. At present, the error >> message differs unnecessarily among subcommands. >> >> * Make "svn" include a unique identifier (such as the apr_err number) >> in its error messages, upon request (by a new cmdline option?), in a >> much briefer form than the maintainer-mode output. e.g. >> >> $ svn ls ^/abc >> svn: E160013: URL 'https://svn.apache.org/repos/asf/abc' >> non-existent in that revision >> > > +1, that's more convenient than looking up translated error messages > (and line numbers) in *.po files. > >> >> - Julian >> >> >> >> On Wed, 2011-01-26, Philip Martin wrote: >>> "C. Michael Pilato" <cmpil...@collab.net> writes: >>> >>>> Would it be possible to, say, provide a mapping between the apr_err code >>>> space and errorcodes? I'm not sure. >>> >>> Not a unique one. >>> >>>> I was thinking that the errorcode >>>> space was limited to 32k distinct values, whereas the apr_err code space is >>>> much, much bigger. (Though, we don't use most of it.) >>> >>> Only 8 bits of the exit() value get back to the parent, so 255 error >>> values. There are currently 271 distinct Subversion SVN_ERRDEFs, plus >>> all the APR ones. >> >> >>
-- C. Michael Pilato <cmpil...@collab.net> CollabNet <> www.collab.net <> Distributed Development On Demand