[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:15:33 CEST

Ben Collins-Sussman <sussman@collab.net> writes:

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

That code used to be in there, then I rewrote the whole way the log
message handling is done, and that feature got lost in the mix.
Sorry, all.

---------------------------------------------------------------------
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:16:59 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.