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

Re: Suggestion: "svn explain"

From: Karl Fogel <kfogel_at_newton.ch.collab.net>
Date: 2002-08-06 00:43:57 CEST

Greg Hudson <ghudson@MIT.EDU> writes:
> Subversion developers may certainly find it easier to communicate in
> terms of "SVN_ERR_NOT_WC" (or whatever) instead of a "Not a working
> copy" error. But I suspect most users, particularly developers, will
> mostly find such a code obstructive.
> If I lose this argument, I would at least suggest downcasing the
> constant name and putting it in parentheses before displaying it to the
> user. Yes, the downcasing could make it a little harder to search the
> Subversion code base for the constant, but if it's in all uppercase then
> the user's attention is called to the less useful information at the
> expense of the more useful information.

I have an idea:

As of today, Subversion does not print the error code (not as a
number, nor as a constant). Let's stick with that for a while and see
what happens. If there's no problem, we'll never notice, and the
issue won't come up again.


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Aug 6 00:59:32 2002

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.