You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by Robert Gonzalez <ro...@gmail.com> on 2009/08/19 18:18:34 UTC
SV_EDITOR not functioning properly on commits
I am using Subversion on Windows XP SP2 at work (both CLI and
Tortoise), and when using the command line client and issuing a commit
command, my default editor (notepad right now) opens up with a log
message from a couple of revisions ago. When I erase the message, add
my new commit message, save it and close it, I get this message from
SVN:
Log message unchanged or not specified
(a)bort, (c)ontinue, (e)dit:
My CLI client is:
> svn --version
svn, version 1.6.4 (r38063)
compiled Aug 5 2009, 12:42:52
In TortoiseSVN everything works fine. The log comments are taken and
published with the commit and all is well. But the client tool seems
to be hosed in some capacity. In the above scenario, if I empty the
original editor window and close it, I get "log message unchanged"
message. So I choose abort and a second editor opens up with a more
recent log message in it. I clear it, close it and I get the same "log
message unchanged" message. I keep choosing abort until it tries to
open a file that is not there and when I edit that and save it and
close it, I get the same "log message unchanged" message.
My question is... how do I fix this so that when I commit from the
command line client it works as I would expect it to? On my home
machine, also an XP SP2 machine running the same version of the CLI
client, everything works.
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=2385334
Re: SV_EDITOR not functioning properly on commits
Posted by Ben Collins-Sussman <su...@red-bean.com>.
Wrong mailing list; send to users@subversion.tigris.org.
On Wed, Aug 19, 2009 at 1:20 PM, Robert
Gonzalez<ro...@gmail.com> wrote:
> Crap. Sorry, it was supposed to be titled SVN_EDITOR.
>
> On Wed, Aug 19, 2009 at 11:18 AM, Robert Gonzalez
> <ro...@gmail.com> wrote:
>>
>> I am using Subversion on Windows XP SP2 at work (both CLI and
>> Tortoise), and when using the command line client and issuing a commit
>> command, my default editor (notepad right now) opens up with a log
>> message from a couple of revisions ago. When I erase the message, add
>> my new commit message, save it and close it, I get this message from
>> SVN:
>>
>> Log message unchanged or not specified
>> (a)bort, (c)ontinue, (e)dit:
>>
>>
>> My CLI client is:
>> > svn --version
>> svn, version 1.6.4 (r38063)
>> compiled Aug 5 2009, 12:42:52
>>
>> In TortoiseSVN everything works fine. The log comments are taken and
>> published with the commit and all is well. But the client tool seems
>> to be hosed in some capacity. In the above scenario, if I empty the
>> original editor window and close it, I get "log message unchanged"
>> message. So I choose abort and a second editor opens up with a more
>> recent log message in it. I clear it, close it and I get the same "log
>> message unchanged" message. I keep choosing abort until it tries to
>> open a file that is not there and when I edit that and save it and
>> close it, I get the same "log message unchanged" message.
>>
>> My question is... how do I fix this so that when I commit from the
>> command line client it works as I would expect it to? On my home
>> machine, also an XP SP2 machine running the same version of the CLI
>> client, everything works.
>
>
> --
> Robert A. Gonzalez
>
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=2385444
Re: SV_EDITOR not functioning properly on commits
Posted by Robert Gonzalez <ro...@gmail.com>.
Crap. Sorry, it was supposed to be titled SVN_EDITOR.
On Wed, Aug 19, 2009 at 11:18 AM, Robert Gonzalez <
robert.anthony.gonzalez@gmail.com> wrote:
> I am using Subversion on Windows XP SP2 at work (both CLI and
> Tortoise), and when using the command line client and issuing a commit
> command, my default editor (notepad right now) opens up with a log
> message from a couple of revisions ago. When I erase the message, add
> my new commit message, save it and close it, I get this message from
> SVN:
>
> Log message unchanged or not specified
> (a)bort, (c)ontinue, (e)dit:
>
>
> My CLI client is:
> > svn --version
> svn, version 1.6.4 (r38063)
> compiled Aug 5 2009, 12:42:52
>
> In TortoiseSVN everything works fine. The log comments are taken and
> published with the commit and all is well. But the client tool seems
> to be hosed in some capacity. In the above scenario, if I empty the
> original editor window and close it, I get "log message unchanged"
> message. So I choose abort and a second editor opens up with a more
> recent log message in it. I clear it, close it and I get the same "log
> message unchanged" message. I keep choosing abort until it tries to
> open a file that is not there and when I edit that and save it and
> close it, I get the same "log message unchanged" message.
>
> My question is... how do I fix this so that when I commit from the
> command line client it works as I would expect it to? On my home
> machine, also an XP SP2 machine running the same version of the CLI
> client, everything works.
--
Robert A. Gonzalez
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=2385335