Scott Palmer <scott.palmer@2connected.org> writes:
> I was just committing some changes and got an error with a not too
> helpful message. I'm wondering if it is related to the message log
> length.. since that is the only thing I was doing differently this
> time around.
>
>
> C:\>set EDITOR=notepad
>
> C:\Workspace\>svn ci
>
> [notepad opens with a list of changed files]
> [I add 8 full lines of log info to the top of the file, save, exit
> notepad]
>
> svn: commit failed (details follow):
>
> C:\Workspace\>
>
>
> As you can see there were no "details" following :)
What were the entire contents of the log message? What files were
changed? Do you have any pre-commit or post-commit hooks installed on
the server, and if so, what do they look like?
> This was the first time I tried to use an editor for the log message,
> previously I simply typed it out on the command line.
> I made sure my workspace was up to date with 'svn up' and tried the
> same thing.. got the same useless error message.
>
> So I did:
>
> C:\Workspace\>svn ci -m "[paste each line of my log here.. all as one
> command line]"
>
> But Windows barfed because the command line got too long and so it
> entered the truncated command. The commit happened with a truncated
> log message. But it committed fine!
>
> Any ideas what it could be?
Yuck. No, I have no idea, off the top of my head, sorry.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Dec 1 17:25:57 2004