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

Re: Repro: Commit Message not stored in Recent Messages (2 instances)

From: Stefan Küng <tortoisesvn_at_gmail.com>
Date: Thu, 04 Oct 2012 19:59:31 +0200

On 02.10.2012 17:04, M Ward wrote:
> I have been able to reproduce a corner case where the Recent Messages is not updated with a recently typed commit message which is then abandoned by closing the commit dialog.
>
> I have seen this before but never worked out why until now.
>
> The repro requires two instances of the commit dialog to be open under the same tree as follows:
>
> 1) Open two "SVN Commit..." dialogs for a folder that has something to commit in it.
>
> 2) In one commit dialog, type some text and then press Esc to close it without committing.
>
> 3) Then in the other commit dialog, press Esc again to close it without committing (do not type any text in the message box).
>
> 4) Open a new "SVN Commit..." dialog for the same folder and press "Recent Messages" => The text typed in 2) has not been recorded.
>
> Closing the second (empty) Commit dialog appears to remove the recent message that was saved by the previous one.
>
> If something _has_ been typed in the second Commit dialog too then it works as expected; both abandoned messages are recorded in Recent Messages.
>
> Hope this makes sense! Thanks.

Created issue #422 for this:
http://code.google.com/p/tortoisesvn/issues/detail?id=422

Stefan

-- 
        ___
   oo  // \\      "De Chelonian Mobile"
  (_,\/ \_/ \     TortoiseSVN
    \ \_/_\_/>    The coolest Interface to (Sub)Version Control
    /_/   \_\     http://tortoisesvn.net
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=3012634
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2012-10-04 19:59:40 CEST

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

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