Colin Watson <cjwatson@flatline.org.uk> writes:
> On Wed, Nov 13, 2002 at 09:44:10AM -0600, Karl Fogel wrote:
> > Note that others have pointed out a directly conflicting itch, which
> > is to have the tmpfile in their local directory. This is not only so
> > it's conveniently available, but also so one will know it cannot be
> > lost due to system sweep (sometimes an automated process sweeps /tmp
> > of files older than X weeks or whatever).
> >
> > For example, suppose you commit using $EDITOR and then walk out the
> > door to go on vacation. The commit fails. You come back three weeks
> > later, see the error message on your screen, and go looking for the
> > log message file. Whups, sorry, svn put it in /tmp, so now it's gone,
> > and you have to rewrite it.
>
> Maybe that kind of thing could be solved by outputting the attempted log
> message after a failed commit?
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".
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Nov 13 18:53:29 2002