Colin Watson <cjwatson@flatline.org.uk> writes:
> > The problem with doing this is that you now have Subversion attempting
> > to perform a non-trivial operation (disk file i/o, as opposed to
> > something easier like a printf() to the screen) while recovering from
> > a failure -- a failure that could have occured for any reason, not the
> > least of which might be: "unable to write to disk".
>
> Well, I was actually thinking more of outputting the log message to
> stdout/stderr, so that when the committer in Karl's example comes back
> to find the error message on the screen, the log message is right after
> it for convenient copying-and-pasting.
Yeah, I thought of that, too. But now you're punishing a guy because
his xterm buffer is too small. No good.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Nov 13 19:02:02 2002