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

Re: long change log entry lost on failed commit - tmp file somewhere?

From: <cmpilato_at_collab.net>
Date: 2002-07-15 23:13:51 CEST

Alexis Huxley <ahuxley@gmx.net> writes:

> Hi again ...
> It's happened a few times that I've done 'svn commit',
> and prepared quite a long change log entry, only to
> have the commit fail.
> I check /tmp, /var/tmp, $TMP_DIR, but there's no
> copy of it there.
> Maybe I've missed the location, but if not and the log
> entry hasn't been saved, would it be possible to do
> so? So, like:
> dione$ svn commit
> <edit long change log entry>
> <commit fails>
> Your commit message has been saved in <wherever>
> dione$
> ?
> Actually, if the SVN team think this is a desirable
> feature, then it's something trivial enough for *me*
> to implement, perhaps I could use it as first step
> into SVN code, and send a patch? :-)

Go for it, but don't underestimate the complexity of the task. All
the log message stuff goes through a funky callback/baton interface,
and when I recently spent half an hour trying to make this very
change, I ended up giving up (and I *know* the code, because I helped
to write it :-))

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Jul 15 22:15:37 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.