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

Re: Failed commit's log message is not remembered

From: Joseph Galbraith <galb_at_vandyke.com>
Date: 2006-04-06 17:36:22 CEST

Daniel Serodio wrote:
> Stefan Küng wrote:
>> On 4/5/06, Daniel Serodio <dserodio@pucsp.br> wrote:
>>> I'm using TortoiseSVN 1.3.2, and I tried to make a commit which failed
>>> because "At least one property change failed".
>>> I corrected this situation, and when I tried to commit it again and
>>> clicked on the "Recent messages" button, the log message I had entered
>>> previously was not remembered.
>>> IMHO, messages for failed commits are the most important to remember,
>>> because I want to use the _exact same text_ I used before.
>>>
>>> Should I file an issue?
>> 1. you can't file an issue - only the devs here can do that
>> 2. can you reproduce the problem? Because honestly, we can't.
>>
>> there have been some few reports similar to this one. But
>> unfortunately, when they tried the same again the log message was
>> saved correctly.
>> So there isn't a reliable reproduction recipe yet, and we haven't
>> found out why this happens. (or if it really even happens - I mean are
>> you *absolutely sure* that you entered a log message at all?).
>>
>> Stefan
>
> 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.
>
> Don't forget to remove the (invalid) config added in step 2.

I believe another way to have this happen (not precisely a bug,
but a feature request, perhaps) is to have the machine rebooted
:-) For example, by the lovely windows update mechanism.

Maybe TortoiseProc could get the shutdown notification and save
the commit message anyway?

Thanks,

Joseph

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Thu Apr 6 17:31:58 2006

This is an archived mail posted to the TortoiseSVN Dev mailing list.

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