On Thu, Jan 17, 2008 at 03:40:24PM -0500, David Glasser wrote:
> On Jan 17, 2008 8:59 AM, Stefan Sperling <stsp_at_elego.de> wrote:
> > On Wed, Jan 16, 2008 at 10:10:16PM +0100, Stefan Küng wrote:
> > >> I am not happy at all either with the current commit error message
> > >> of the CLI client. It should at least point the user where to get more
> > >> information. This applies to all conflicts.
> > >
> > > One think I don't quite understand: why is there such a limit in the svn
> > > client? Is this documented somewhere?
> > http://subversion.tigris.org/hacking.html#error-messages
> That says 70 characters, not 50. And we have broken the newline rule
> before; see libsvn_wc/questions.c(compare_and_verify and
> svn_wc__check_format), say.
Right, so printing "run command xyz to get more information"
as a seperate line in an error message should be OK?
And what about including potentially rather long multi-line tree conflict
descriptions in error messages? Like the ones that are currently also
shown by "svn info" on the tree-conflicts branch?
Stefan Sperling <stsp_at_elego.de> Software Developer
elego Software Solutions GmbH HRB 77719
Gustav-Meyer-Allee 25, Gebaeude 12 Tel: +49 30 23 45 86 96
13355 Berlin Fax: +49 30 23 45 86 95
http://www.elego.de Geschaeftsfuehrer: Olaf Wagner
Received on 2008-01-19 01:48:08 CET
- application/pgp-signature attachment: stored