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

SVN commit log issues (CLI 1.6.4 on WinXP SP2)

From: Robert Gonzalez <robert_at_robert-gonzalez.com>
Date: Mon, 14 Sep 2009 16:32:46 -0700

I have run into a problem recently that I don't know how to solve. Google is
not being my friend and neither is the SVN manual.

When I attempt to commit my changes from the command line on Windows my
editor opens up with an old commit log message. It also does not have the
svn status of changed/added/deleted files in it. When I delete the log
message that is in the editor and replace it then save it and exit my
editor, I get the following message from SVN:

*Code:*Log message unchanged or not specified
(a)bort, (c)ontinue, (e)dit:

If I choose continue the commit happens but without a log message. If I
choose edit, another svn-commit.tmp file opens, this time #2, with a
different old log message. When I change that, save it and exit the editor,
I get the same message from SVN. In fact, I get this message no matter what
I do when committing from the command line, regardless of which editor I am
using (I have tried this with vim, Notepad, Notepad2 and Notepad++, all with
the same result). SVN just keeps making a bunch of svn-commit.tmp files, and
it always seems to keep the oldest three messages in the first of the three
commit message log files.

I can definitely pass the message with the -m flag, and I can also send the
message when using tortoise. This is only happening from the command line in
Windows (XP SP2).

SVN Client details:
*Code:*C:\>svn --version
svn, version 1.6.4 (r38063)
   compiled Aug 5 2009, 12:42:52

Copyright (C) 2000-2009 CollabNet.
Subversion is open source software, see http://subversion.tigris.org/
This product includes software developed by CollabNet (

The following repository access (RA) modules are available:

* ra_neon : Module for accessing a repository via WebDAV protocol using
  - handles 'http' scheme
  - handles 'https' scheme
* ra_svn : Module for accessing a repository using the svn network
  - with Cyrus SASL authentication
  - handles 'svn' scheme
* ra_local : Module for accessing a repository on local disk.
  - handles 'file' scheme
* ra_serf : Module for accessing a repository via WebDAV protocol using
  - handles 'http' scheme
  - handles 'https' scheme

My question is, how do I fix this? I just want SVN to forget about the old
commit message logs and let me commit with the current status. What do I
need to do?

Robert Gonzalez
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-09-15 01:44:19 CEST

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.