Re: Failed commit's log message is not remembered

Daniel Serodio wrote:

> I'm absolutely sure. I'm able to reproduce it with the following recipe:
>
> 1) Checkout some project
> 2) Edit your Subversion 'config' file, adding:
> *.foo = svn:mime-type:text/plain
> (note wrong syntax for the property value)
> 3) Create an empty.foo file in your working copy
> 4) Ask TortoiseSVN to Add this file (it will set an invalid property
> thanks to the typo in the 'config' file)
> 5) Ask TortoiseSVN to Commit
> 6) Type a log message.
> 7) Subversion rejects the commit, "At least one propety change failed;
> repository is unchanged"
> 8) Ask TortoiseSVN to Commit the file again
> 9) Click Recent Messages
> 10) The log message typed in 6) is not there.

Now, we have a problem. I can't reproduce this.
First I tried with a local (file:///) repository. Strange thing is that
committing the illegal property works here. And of course, the log
message was saved correctly.
Then, I tried the same with https:// access. This time, I got the error.
But still, the log message was saved.

> Don't forget to remove the (invalid) config added in step 2.

Good thing you mentioned this - I almost forgot it (seriously!) :)

Stefan

-- 
        ___
   oo  // \\      "De Chelonian Mobile"
  (_,\/ \_/ \     TortoiseSVN
    \ \_/_\_/>    The coolest Interface to (Sub)Version Control
    /_/   \_\     http://tortoisesvn.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org