On Thu, Sep 25, 2003 at 05:16:32PM +0100, Julian Foad wrote:
> Yes, that would be possible, but I think Subversion's
> behaviour should be changed. Let's see what other people
> think.
If the editor's exit code is not 0, svn won't commit. If you
are desperate, you can kill the editor (experiment before
depending on this). Otherwise wrap your editor with a
script that gives you the option of raising a non-zero code.
An alternative is not to save the log message file. (If you
have repetitious-save-syndrome, this won't help you much.) If
the file is unmodified, you'll be asked whether you want to
abort the commit.
But on the whole, this problem is one of wanting interactive
behaviour from a command. You typed in commit; so svn
commits. Had you supplied a message on the command line, the
commit would have been done without you being able to stop
it. Instead, there is a pause so you can supply a message,
before proceeding without you being able to stop it. ;-)
This pause for a message is not intended to be a 'last exit
before toll road.' The last exit was hitting enter on the
command line.
This topic has come up before. The 'really commit?' question
would tend to get answered unconsciously after the first few
dozen times. The safety net it seems to offer is only an
illusion.
Bruce
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Sep 26 03:47:36 2003