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

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? :-)

I swear that this code *does* exist already... I remember *seeing* it
happen to me before: "your message has been saved in XXXX".

Maybe that codepath isn't executing anymore for some reason?

---------------------------------------------------------------------
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:05:36 2002